Bug#837121: gazebo: please restrict libkido-dev (build-)dependency to architectures where it is available.

[Jeremy Bicha]

The changelog says restrict libkido to ppc64el (etc.) but
debian/control says powerpc. I believe ppc64el is what you want.

Thanks,
Jeremy Bicha

Processed: python-ofxclient: chokes on %{secured}

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/captin411/ofxclient/issues/28
Bug #837208 [python-ofxclient] python-ofxclient: chokes on %{secured}
Set Bug forwarded-to-address to 
'https://github.com/captin411/ofxclient/issues/28'.

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

Bug#837208: python-ofxclient: chokes on %{secured}

[Clint Adams]

Package: python-ofxclient
Version: 2.0.2-1
Severity: serious
Control: forwarded -1 https://github.com/captin411/ofxclient/issues/28

Traceback (most recent call last):
  File "/usr/bin/ofxclient", line 9, in 
load_entry_point('ofxclient==2.0.2', 'console_scripts', 'ofxclient')()
  File "/usr/lib/python2.7/dist-packages/ofxclient/cli.py", line 60, in run
main_menu()
  File "/usr/lib/python2.7/dist-packages/ofxclient/cli.py", line 80, in 
main_menu
add_account_menu()
  File "/usr/lib/python2.7/dist-packages/ofxclient/cli.py", line 127, in 
add_account_menu
if login_check_menu(bank):
  File "/usr/lib/python2.7/dist-packages/ofxclient/cli.py", line 215, in 
login_check_menu
GlobalConfig.add_account(a)
  File "/usr/lib/python2.7/dist-packages/ofxclient/config.py", line 246, in 
add_account
self.encrypt_account(id=section_id)
  File "/usr/lib/python2.7/dist-packages/ofxclient/config.py", line 254, in 
encrypt_account
self.parser.set_secure(id, key, value)
  File "/usr/lib/python2.7/dist-packages/ofxclient/config.py", line 134, in 
set_secure
ConfigParser.set(self, section, option, value)
  File "/usr/lib/python2.7/dist-packages/configparser.py", line 1233, in set
super(ConfigParser, self).set(section, option, value)
  File "/usr/lib/python2.7/dist-packages/configparser.py", line 930, in set
value)
  File "/usr/lib/python2.7/dist-packages/configparser.py", line 409, in 
before_set
u"position %d" % (value, tmp_value.find(u'%')))
ValueError: invalid interpolation syntax in u'%{secured}' at position 0

Bug#837123: [anna] segfault in wheezy installer

[Vincent McIntyre]

On Fri, Sep 09, 2016 at 03:59:17PM +0200, Aurelien Jarno wrote:
> 
> I don't talk about the software running on your DNS servers, but
> rather how they behave when they get queried. It might depends on
> many other things, like if your network has IPv6 or not.
> 
> Note that's only one explanation, not sure it's the right one, but
> given I am unable to reproduce the issue, it's the only one that
> come to my mind.

Thank you for explaining. I am struggling with this idea since AFAIK
the DNS servers have not been changed in the last six months or more
so I can think of no reason for the behaviour to have changed.
That history is what makes me think something must have changed in
the installer around the time of the last point release (May).
But from what you say that isn't the case.

You've given me a few things to try out
 - tell DHCP to supply different DNS servers (running bind)
 - make sure all ipv6 related options are disabled
   and no ipv6 DNS entries exist for the target host
 - make sure all ipv6 related options are enabled
   and valid ipv6 DNS entries exist for the target host

Also I can try installing oldstable with the jessie installer.
 
If all of that makes no difference, what would be the next step?
I assume I'd have to build a debug version of the installer
and try to get a backtrace?
My concern is there's a segfault still lurking in the stretch
version. If we can squash it here that fix could be forward-ported.

Kind regards
Vince

Processed: severity of 837130 is serious, severity of 837198 is serious, tagging 834156, tagging 836816 ...

[Debian Bug Tracking System]

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

> severity 837130 serious
Bug #837130 [src:vim] vim package cannot be installed because of missing 
dependency
Severity set to 'serious' from 'normal'
> severity 837198 serious
Bug #837198 {Done: Mario Limonciello } [fwupdate] 
fwupdate not buildable on armhf and arm64, unsatisifiable build-dependency.
Severity set to 'serious' from 'normal'
> tags 834156 + sid stretch
Bug #834156 {Done: Clint Adams } [haskell-devscripts] yi: 
FTBFS: libicuuc.so.55: cannot open shared object file: No such file or directory
Added tag(s) stretch and sid.
> tags 836816 + sid
Bug #836816 [calligra-l10n-bs] calligra-l10-*: not installable in sid
Added tag(s) sid.
> tags 836874 + sid
Bug #836874 [sentinella] sentinella: not installable in sid
Added tag(s) sid.
> thanks
Stopping processing here.

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

Processed: Re: Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #837178 [src:linux] linux-image-3.16.0-4-amd64: All memory and swap is used 
up until system freezes
Severity set to 'normal' from 'critical'

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

Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Ben Hutchings]

Control: severity -1 normal

On Fri, 2016-09-09 at 15:37 -0400, Wolfgang Tichy wrote:
> Package: src:linux
> Version: 3.16.7-ckt25-2+deb8u3
> Severity: critical
> Tags: security
> Justification: causes serious data loss
> 
> Dear Maintainer,
> 
> when I open a particular word document (it contains images and I can send it
> to you for testing) with libreoffice, all memory and all swap get used up
> within about a minute. This happens slowly enough that it can be monitored
> with "top" and "free". What I see with top is that soffice.bin (which is
> libreoffice) does not use much memory (maybe 2%). Nevertheless more and more
> memory gets used.

>  "free -h" gives something like this:
> 
>  total   used   free sharedbuffers cached
> Mem:  7.5G   7.4G   141M   5.9G71M   6.4G
> -/+ buffers/cache:   917M   6.6G
> Swap: 8.0G   663M   7.4G
> 
> Eventually the "used" column in the "Mem:" and "Swap:" and lines reach the
> total and the system runs out of memory and becomes totally unresponsive
> (even the mouse pointer freezes), no remote logins are possible at this
> point, and all keypresses are ignored. The only way to regain control is by
> holding down the power button for 10s.

Alt-SysRq Alt-K would probably work.

> However, the "used" column in the
> "-/+ buffers/cache:" line stays near 1GB, so that it is clear that
> buffers/caches take up almost all the space.
>
> You may wonder why I file this against the kernel and not libreoffice. Well,
> I am sure libreoffice is doing something stupid, that could be fixed to
> circumvent this problem. But the kernel should simply not allow any user
> process to bring down the entire system. Also it seems the kernel is
> allocating caches or buffers until it runs out of all memory and then
> freezes.

A large number for caches or buffers does not indicate a problem.  That
is absolutely normal.  I think the problem is the 'shared' memory; that
very likely corresponds to graphics buffers (shared between
LibreOffice, the X server and the kernel graphics driver).

[...]
> On this one, Gnome3 crashes and dmesg has a lot of lines lines like:
> [880754.926611] [TTM] Failed to find memory space for buffer 
> 0x880367e42800 eviction
> [880754.926613] [TTM] No space for 880367e42800 (497 pages, 1988K, 1M)
> [880754.926614] [TTM]   placement[0]=0x00070002 (1)
> [880754.926616] [TTM] has_type: 1
> [880754.926617] [TTM] use_type: 1
> [880754.926618] [TTM] flags: 0x000A
> [880754.926619] [TTM] gpu_offset: 0x
> [880754.926620] [TTM] size: 131072
> [880754.926621] [TTM] available_caching: 0x0007
> [880754.926622] [TTM] default_caching: 0x0001
[...]

And that's an attempt to allocate such a graphics buffer.

> This is actually good because after the gnome3 crash the system is still
> usable. I should say that in all cases I am using the open source graphics
> drivers that use kernel mode setting. So the latter crash leads me to think
> that some interaction between the graphics drivers and the kernel leads to
> the allocation of too many buffers/caches by the kernel until it runs out.
> Probably this is all triggered by libreoffice (running on X) trying to
> display some JPG images in a document.
> 
> The reason why I consider this security relevant is that anybody with a user
> account can use libreoffice to bring the system down.

This sounds like CVE-2013-7445 which is unlikely to be fixed in jessie.

> This will cause data loss since all other users cannot save any data in open
> files.

Losing data from memory doesn't count.  But please do open bugs on
applications that don't implement auto-save.

Ben.

-- 
Ben Hutchings
Design a system any fool can use, and only a fool will want to use it.

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

Bug#836669: caja: Crashes due to theme errors

[Frank McCormick]

Package: caja
Version: 1.14.2-1
Followup-For: Bug #836669

Caja just stated doing this: click on home icon on
desktop...all desktop icons disappear for a moment,
then return but caja never opens directory. Syslog and kernel log
show segfault. .xsessions-error file is full of gtk errors.
Change theme same story.


-- 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/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages caja depends on:
ii  caja-common   1.14.2-1
ii  desktop-file-utils0.23-1
ii  gvfs  1.29.91-1
ii  libatk1.0-0   2.21.90-2
ii  libc6 2.23-5
ii  libcairo-gobject2 1.14.6-1+b1
ii  libcairo2 1.14.6-1+b1
ii  libcaja-extension11.14.2-1
ii  libexempi32.3.0-2
ii  libexif12 0.6.21-2
ii  libgail-3-0   3.21.5-3
ii  libgdk-pixbuf2.0-02.34.0-1
ii  libglib2.0-0  2.49.6-1
ii  libglib2.0-data   2.49.6-1
ii  libgtk-3-03.21.5-3
ii  libice6   2:1.0.9-1+b1
ii  libmate-desktop-2-17  1.14.1-1
ii  libpango-1.0-01.40.2-1
ii  libpangocairo-1.0-0   1.40.2-1
ii  libselinux1   2.5-3
ii  libsm62:1.2.2-1+b1
ii  libstartup-notification0  0.12-4
ii  libunique-3.0-0   3.0.2-2
ii  libx11-6  2:1.6.3-1
ii  libxext6  2:1.3.3-1
ii  libxml2   2.9.4+dfsg1-1+b1
ii  libxrender1   1:0.9.9-2
ii  mate-desktop  1.14.1-1
ii  shared-mime-info  1.6-1

Versions of packages caja recommends:
ii  gvfs-backends  1.29.91-1

Versions of packages caja suggests:
ii  engrampa1.14.1-1
pn  gstreamer1.0-tools  
pn  meld

-- no debconf information

Bug#811991: marked as done (hyperrogue: FTBFS with GCC 6: call overloaded is ambiguous)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 23:35:20 +
with message-id 
and subject line Bug#811991: fixed in hyperrogue 8.3j+dfsg-1
has caused the Debian Bug report #811991,
regarding hyperrogue: FTBFS with GCC 6: call overloaded is ambiguous
to be marked as done.

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

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


-- 
811991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hyperrogue
Version: 4.2+dfsg-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-overloaded-ambiguous

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.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> make[2]: Entering directory '/<>/hyperrogue-4.2+dfsg'
> g++ hyper.cpp -o hyper -lSDL -lSDL_ttf -lSDL_mixer -lfontconfig -DFHS -Wall 
> -g -lSDL_gfx -g -O2 -fPIE -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -pie 
> -Wl,-z,relro -Wl,-z,now -lGL -O3
> In file included from hyper.cpp:62:0:
> game.cpp:2216:14: warning: invalid suffix on literal; C++11 requires a space 
> between literal and string macro [-Wliteral-suffix]
>fprintf(f, "HyperRogue: game statistics (version "VER")\n");
>   ^
> 
> In file included from hyper.cpp:63:0:
> graph.cpp:1398:3: warning: invalid suffix on literal; C++11 requires a space 
> between literal and string macro [-Wliteral-suffix]
>"Welcome to HyperRogue! (version "VER")\n"
>^
> 
> hyper.cpp:67:10: warning: invalid suffix on literal; C++11 requires a space 
> between literal and string macro [-Wliteral-suffix]
>printf("HyperRogue by Zeno Rogue , version "VER"\n");
>   ^
> 
> In file included from hyper.cpp:58:0:
> hyperpoint.cpp: In function 'transmatrix xpush(ld)':
> hyperpoint.cpp:115:24: error: call of overloaded 'cosh(ld&)' is ambiguous
>T[0][0] = +cosh(alpha); T[0][2] = +sinh(alpha);
> ^
> 

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: hyperrogue
Source-Version: 8.3j+dfsg-1

We believe that the bug you reported is fixed in the latest version of
hyperrogue, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 811...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated hyperrogue package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 10 Sep 2016 00:17:25 +0200
Source: hyperrogue
Binary: hyperrogue hyperrogue-music
Architecture: source
Version: 8.3j+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 hyperrogue - non-euclidean graphical rogue-like game
 hyperrogue-music - in-game music for hyperrogue
Closes: 797024 797974 811991
Changes:
 hyperrogue (8.3j+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 8.3j+dfsg. (Closes: #797024)
   * New upstream release fixes FTBFS with GCC-6. (Closes: #811991)
   * Drop hyperrogue-dbg package and use the automatic -dbgsym package instead.
   * Declare compliance with Debian Policy 3.9.8.
   * Vcs-fields: Use cgit and https.
   * hyperrogue-music: Suggest hyperrogue.
   * hyperrogue.desktop: Add a comment in German.
   * Drop hyperrogue.menu, remove hyperrogue.xmp icon and do not convert
 the png icon to xpm anymore. (Closes: #797974)
   * d/rules: Change source directory to src.
   * Add system-dejavu.patch and replace 10-fontconfig.patch.
   * Drop 01-sdl_wm.patch. Fixed upstream.
   * d/control: Only depend on fonts-dejavu-core for hyperrouge.
   * 

Bug#834964: testresources: undeterministic test still runs and fails with probability 1/12

[Santiago Vila]

retitle 834964 testresources: undeterministic test still runs and fails with 
probability 1/12
thanks

On Fri, 9 Sep 2016, Thomas Goirand wrote:

> With an up-to-date Sid, I couldn't reproduce this issue. Therefore, I'm
> closing this bug. Feel free to continue discussing it even when it has
> the closed status if you want to continue investigating.

You already investigated this and tried to fix it.

The changelog reads like this:

testresources (1.0.0-1) unstable; urgency=medium

  * Do not run undeterministic test:
- test_optimising_test_suite.TestGraphStuff.testBasicSortTests

and debian/rules reads like this:

ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
nosetests -v 
--exclude=testresources.tests.test_optimising_test_suite.TestGraphStuff.testBasicSortTests
nosetests3 -v 
--exclude=testresources.tests.test_optimising_test_suite.TestGraphStuff.testBasicSortTests
endif

So, there is a clear intention to disable the test because of it not
being deterministic (it fails approximately 1/12 of the time).

The only problem is that the way it's being disabled does not seem to
work, and the test still runs.

So, unless you disagree with yourself, this bug should be reopened and
the test should be really disabled.

Thanks.

Processed: testresources: undeterministic test still runs and fails with probability 1/12

[Debian Bug Tracking System]

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

> retitle 834964 testresources: undeterministic test still runs and fails with 
> probability 1/12
Bug #834964 {Done: Thomas Goirand } [src:testresources] 
testresources: FTBFS too much often (failing tests)
Changed Bug title to 'testresources: undeterministic test still runs and fails 
with probability 1/12' from 'testresources: FTBFS too much often (failing 
tests)'.
> thanks
Stopping processing here.

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

Bug#818443: marked as done (sdate: FTBFS: libtool: Version mismatch error)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 22:58:01 +
with message-id 
and subject line Bug#818443: fixed in sdate 0.4+nmu1
has caused the Debian Bug report #818443,
regarding sdate: FTBFS: libtool: Version mismatch error
to be marked as done.

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

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


-- 
818443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sdate
Version: 0.4
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[2]: Leaving directory '/<>/obj'
> cd objfake && /usr/bin/make
> make[2]: Entering directory '/<>/objfake'
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"sdate\" 
> -DPACKAGE_TARNAME=\"sdate\" -DPACKAGE_VERSION=\"0.4\" 
> -DPACKAGE_STRING=\"sdate\ 0.4\" -DPACKAGE_BUGREPORT=\"c...@df7cb.de\" 
> -DPACKAGE_URL=\"\" -DPACKAGE=\"sdate\" -DVERSION=\"0.4\" -DSTDC_HEADERS=1 
> -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBDL=1 -I. 
> -I../fake   -Wdate-time -D_FORTIFY_SOURCE=2  -W -Wall -g -O2 -MT libsdate.lo 
> -MD -MP -MF .deps/libsdate.Tpo -c -o libsdate.lo ../fake/libsdate.c
> libtool: Version mismatch error.  This is libtool 2.4.6 Debian-2.4.6-0.1, but 
> the
> libtool: definition of this LT_INIT comes from libtool 2.4.2.
> libtool: You should recreate aclocal.m4 with macros from libtool 2.4.6 
> Debian-2.4.6-0.1
> libtool: and run autoconf again.
> Makefile:441: recipe for target 'libsdate.lo' failed
> make[2]: *** [libsdate.lo] Error 63

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: sdate
Source-Version: 0.4+nmu1

We believe that the bug you reported is fixed in the latest version of
sdate, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 818...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated sdate package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Sep 2016 00:06:27 +0200
Source: sdate
Binary: sdate
Architecture: source amd64
Version: 0.4+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Berg 
Changed-By: Axel Beckert 
Description:
 sdate  - never ending September date
Closes: 818443
Changes:
 sdate (0.4+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS by running autoreconf also inside the subdirectory
 "fake". (Closes: #818443)
   * Additionally also remove config.h.in, fake/Makefile.in,
 fake/aclocal.m4, and fake/configure in the clean target.
Checksums-Sha1:
 d2f61a2e4ac7751f91198e12b172f30b083a5a9d 1511 sdate_0.4+nmu1.dsc
 6b06532923911279b43ba45712b922a630871cdc 35055 sdate_0.4+nmu1.tar.gz
 f931156645151d62f03ab6e9607652118a2a8d15 6610 sdate-dbgsym_0.4+nmu1_amd64.deb
 2785763cf83fe8c3252f156a02ade2cd4bad300c 10306 sdate_0.4+nmu1_amd64.deb
Checksums-Sha256:
 d4699f43b7adff0397f9f9ed9d560ac41038b22210a4a9dc1dc361a252269719 1511 
sdate_0.4+nmu1.dsc
 f3ba631faf903cbad858dbc4345fe41146c5a96da1cf1492a8d9fa60ce3edf05 35055 
sdate_0.4+nmu1.tar.gz
 05253e53dfea19c12b5e26f0e9ff51c75cc59f38810db01f593266ff169645c3 6610 
sdate-dbgsym_0.4+nmu1_amd64.deb
 b3a3f37fa1f2df73d382c7116091b1cd678e96a0d16a041950e76c739a4dd2aa 10306 
sdate_0.4+nmu1_amd64.deb
Files:
 c99bbc3b550e9125070446d5899c8bd3 1511 utils optional sdate_0.4+nmu1.dsc
 325336fb80bd460bea2db3daf4ac74f3 35055 utils optional sdate_0.4+nmu1.tar.gz
 bcb3386eee50fe79eb76eb02679da1a5 6610 debug extra 
sdate-dbgsym_0.4+nmu1_amd64.deb
 249a167d56af5bd6ce5b334fab430724 10306 utils optional sdate_0.4+nmu1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX0zcXAAoJEGvmY8daNcl1uHAP/2X7jfmwW/FKKP0TQ+Xf8GWf
dBIK4V11oEQnDgy4uddxmHjNLvhRBa0dk1td2bzUo67/PpZN20yf/Ix1XZSof4j6
TWngTyt+4pA3LGFkGIPFF+4diYBa7+L3s3aDDMDDF0ZMGihQhEhoQMb80JqoPwID

Processed: Re: [Patch+NMU] Re: Bug#818443: sdate: FTBFS: libtool: Version mismatch error

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + pending
Bug #818443 [sdate] sdate: FTBFS: libtool: Version mismatch error
Added tag(s) pending.

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

Bug#837192: uninstallable in sid (not compatible with GNOME 3.21/3.22)

[Sébastien Villemot]

Package: gnome-shell-pomodoro
Version: 0.11.2-2
Severity: serious

Dear Maintainer,

GNOME 3.21.90 has entered sid (and GNOME 3.22 should follow soon).

This makes gnome-shell-pomodoro uninstallable. Please upgrade.

Cheers,

-- 
 .''`.Sébastien Villemot
: :' :Debian Developer
`. `' http://sebastien.villemot.name
  `-  GPG Key: 4096R/381A7594


signature.asc
Description: PGP signature

Processed: Bug#837090 marked as pending

[Debian Bug Tracking System]

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

> tag 837090 pending
Bug #837090 {Done: Craig Small } [src:wordpress] wordpress: 
CVE-2016-6896 CVE-2016-6897
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837090: marked as pending

[Craig Small]

tag 837090 pending
thanks

Hello,

Bug #837090 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=collab-maint/wordpress.git;a=commitdiff;h=8f8575b

---
commit 8f8575b8132884811063c7fefbd7aaf0825a7e71
Author: Craig Small 
Date:   Sat Sep 10 07:53:57 2016 +1000

backport changeset 38538

sanitize the title from the uploaded filename.
Fixes CVE-2016-6896

References:
 https://core.trac.wordpress.org/changeset/38538

diff --git a/debian/changelog b/debian/changelog
index fcadd38..eeb8780 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+wordpress (4.1+dfsg-1+deb8u10) UNRELEASED; urgency=high
+
+  * Backport patches from 4.6.1/4.1.13 Closes: #837090
+  * CVE-2016-6897 not vulnerable
+  * Changeset 38538 santize filename CVE-2016-6896
+
+ -- Craig Small   Sat, 10 Sep 2016 07:46:59 +1000
+
 wordpress (4.1+dfsg-1+deb8u9) jessie-security; urgency=high
 
   * Backport patches from 4.5.3/4.1.12 Closes: #828225

Bug#818443: [Patch+NMU] Re: Bug#818443: sdate: FTBFS: libtool: Version mismatch error

[Axel Beckert]

Control: tag -1 + patch

Hi Christoph,

Martin Michlmayr wrote:
> > libtool: Version mismatch error.  This is libtool 2.4.6 Debian-2.4.6-0.1, 
> > but the
> > libtool: definition of this LT_INIT comes from libtool 2.4.2.
> > libtool: You should recreate aclocal.m4 with macros from libtool 2.4.6 
> > Debian-2.4.6-0.1
> > libtool: and run autoconf again.
> > Makefile:441: recipe for target 'libsdate.lo' failed
> > make[2]: *** [libsdate.lo] Error 63

Reason for this seems that "--with autoreconf" only runs autoreconf in
the root directory, but not in the subdirectory "fake".

So the following patch suffices to fix the FTBFS for me:

diff -Nru sdate-0.4/debian/rules sdate-0.4+nmu1/debian/rules
--- sdate-0.4/debian/rules  2014-04-25 10:42:03.0 +0200
+++ sdate-0.4+nmu1/debian/rules 2016-09-09 23:10:42.0 +0200
@@ -14,6 +14,7 @@
 override_dh_auto_configure:
mkdir obj objfake
cd obj && CFLAGS="$(CFLAGS)" ../configure --prefix=/usr 
--mandir=/usr/share/man --libdir=/usr/lib/libsdate
+   cd fake && autoreconf -f
cd objfake && CFLAGS="$(CFLAGS)" ../fake/configure --prefix=/usr 
--mandir=/usr/share/man
 
 override_dh_auto_build:

dh_autoreconf can't be called twice, hence I had to call autoreconf
manually. So this doesn't clean up any changes autoreconf made, and
hence, if I build the package twice in a row, I get a larger diff:

 config.h.in  |  119 --
 debian/rules |1 
 fake/Makefile.in |   54 -
 fake/aclocal.m4  | 2741 +++
 fake/configure   | 2080 +

So I actually recommend to also remove config.h.in, fake/Makefile.in,
fake/aclocal.m4, and fake/configure in the clean target, too.

Accordingly that diffstat looks much more sane:

 config.h.in  |  119 
 debian/rules |3 
 fake/Makefile.in |  811 ---
 fake/aclocal.m4  | 9788 -
 fake/configure   |14453 ---

Also the source package became much smaller:

-rw-r--r-- 1 abe abe 225702 Apr 25  2014 ../sdate_0.4.tar.gz
-rw-r--r-- 1 abe abe  35152 Sep  9 23:45 ../sdate_0.4+nmu1.tar.gz

So the full patch for that is:

diff -Nru sdate-0.4/debian/rules sdate-0.4+nmu1/debian/rules
--- sdate-0.4/debian/rules  2014-04-25 10:42:03.0 +0200
+++ sdate-0.4+nmu1/debian/rules 2016-09-09 23:10:42.0 +0200
@@ -14,6 +14,7 @@
 override_dh_auto_configure:
mkdir obj objfake
cd obj && CFLAGS="$(CFLAGS)" ../configure --prefix=/usr 
--mandir=/usr/share/man --libdir=/usr/lib/libsdate
+   cd fake && autoreconf -f
cd objfake && CFLAGS="$(CFLAGS)" ../fake/configure --prefix=/usr 
--mandir=/usr/share/man
 
 override_dh_auto_build:
@@ -24,7 +25,7 @@
cd obj && $(MAKE) check
 
 override_dh_clean:
-   rm -rf build-stamp .deps obj objfake autom4te.cache
+   rm -rf build-stamp .deps obj objfake autom4te.cache config.h.in 
fake/Makefile.in fake/aclocal.m4 fake/configure
dh_clean
 
 override_dh_auto_install:

I'll try to make up an NMU for this. Since this package is marked
LowThresholdNMU and since I know that you won't be mad at me, I'll
upload it as soon as I got a proper NMU. :-) Will post the full
debdiff afterwards.

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


signature.asc
Description: Digital signature

Processed: [Patch+NMU] Re: Bug#818443: sdate: FTBFS: libtool: Version mismatch error

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #818443 [sdate] sdate: FTBFS: libtool: Version mismatch error
Added tag(s) patch.

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

Bug#837090: wordpress: CVE-2016-6896 CVE-2016-6897

[Craig Small]

On Fri, Sep 9, 2016 at 3:39 AM Salvatore Bonaccorso 
wrote:

> the following vulnerabilities were published for wordpress.
>
> CVE-2016-6896[0] and CVE-2016-6897[1]. It was reported that they at
> least affect 4.5.3, no earlier version were so far checked, since no
> full details to fixes given. There are more information in [2].
>

It's a little more complicated than that with three vulnerabilities and the
identification a bit mixed up. So here goes.

CSRFcheck done too late.
This is CVE-2016-6897, oss-sec correctly broke the two issues out due to
different versions being impacted. It was (silently?) fixed for wordpress
4.6 but that didn't get updated (I missed the 4.6 announcement) so sid was
still vulnerable until I uploaded 4.6.1
Reported in wordpress 37490 and fixed in changeset 38168.

Directory traversal
This is CVE-2016-6896. Wordpress 4.6.1 reports this as " a cross-site
scripting vulnerability via image filename, reported by SumOfPwn researcher
Cengiz Han Sahin". Fixed in changeset 38538.

Upgrade Package Uploader
This has no CVE. Wordpress 4.6.1 reports this as "path traversal
vulnerability in the upgrade package uploader, reported by Dominik
Schilling". Fixed in changeset 38524.

The first changeset is simple with the other two being trivial. I will
start to look at jessie and see if that version is impacted. My initial
hunch is it will be. Expect a debdiff shortly!

 - Craig

Bug#836995: texlive-base: fails to upgrade wheezy -> jessie -> stretch

[Norbert Preining]

tags 836995 + pending
thanks

Hi Andreas,

> Severity: serious

Not sure if this is really serious. Updates are only supported from
one version to the next. I cannot take care about non-existing
packages in one version when upgrading to the next. Users are 
supposed to remove all outdated packages before updating to a new
release.

Anyway, added necessary breaks/replaces.

Norbert

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

Processed: Re: Bug#836995: texlive-base: fails to upgrade wheezy -> jessie -> stretch

[Debian Bug Tracking System]

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

> tags 836995 + pending
Bug #836995 [texlive-base] texlive-base: fails to upgrade wheezy -> jessie -> 
stretch
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#834180 marked as pending

[Debian Bug Tracking System]

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

> tag 834180 pending
Bug #834180 {Done: Herbert Parentes Fortes Neto } 
[src:bristol] bristol: FTBFS: audioEngineJack.c:42:26: fatal error: 
alsa/iatomic.h: No such file or directory
Ignoring request to alter tags of bug #834180 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#834180: marked as pending

[IOhannes m zmölnig]

tag 834180 pending
thanks

Hello,

Bug #834180 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-multimedia/bristol.git;a=commitdiff;h=a90388f

---
commit a90388f843f73f6c8a57576068e4a8733589521f
Author: IOhannes m zmölnig 
Date:   Fri Sep 9 22:01:52 2016 +0200

Updated d/changelog

Gbp-Dch: ignore

diff --git a/debian/changelog b/debian/changelog
index 0e629f9..d993c3b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+bristol (0.60.11-3) unstable; urgency=medium
+
+  * Team upload.
+  * debian/copyright:
+  - Put my name in 'Files: debian/*' entry.
+  * debian/patches:
+  - 03-rm_alsa-iatomic.h.patch added. (Closes: #834180)
+Thanks Adrian Bunk and James Cowgill.
+
+ -- Herbert Parentes Fortes Neto   Fri, 09 Sep 2016 09:04:38 
-0300
+
 bristol (0.60.11-2) unstable; urgency=low
 
   * Upload to unstable.

Processed: Re: Bug#837153: pdns-recursor fails to start because of missing protobuf library

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #837153 [pdns-recursor] pdns-recursor fails to start because of missing 
protobuf library
Severity set to 'normal' from 'grave'
> tags -1 + unreproducible
Bug #837153 [pdns-recursor] pdns-recursor fails to start because of missing 
protobuf library
Added tag(s) unreproducible.

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

Bug#837153: pdns-recursor fails to start because of missing protobuf library

[Christian Hofstaedtler]

Control: severity -1 normal
Control: tags -1 + unreproducible

* Sérgio Carvalho  [160909 11:21]:
> Package: pdns-recursor
> Version: 4.0.2-1

> pdns-recursor in recently updated debian sid installations fails to
> start with the error:
> 
> /usr/sbin/pdns_recursor: symbol lookup error: /usr/sbin/pdns_recursor:
> undefined symbol: _ZN6google8protobuf15UnknownFieldSet9AddVarintEim
> 
> I believe the package is linked to a no longer existing libprotobuf.

Thank you for your report, but I can not reproduce this in Debian
sid.

> ii  libprotobuf10  3.0.0-7

ii  libprotobuf10:amd64 3.0.0-7  amd64
ii  pdns-recursor   4.0.2-1  amd64

# /usr/sbin/pdns_recursor --daemon=no --write-pid=no --disable-syslog
Sep 09 19:50:28 PowerDNS Recursor 4.0.2 (C) 2001-2016 PowerDNS.COM BV
Sep 09 19:50:28 Using 64-bits mode. Built using gcc 6.2.0 20160901.
[..]

Also, 4.0.2-1 was built using libprotobuf10 3.0.0-7, so I can not see
how this version would reference symbols that no longer exist in 3.0.0-7.

Best,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#837178: linux-image-3.16.0-4-amd64: All memory and swap is used up until system freezes

[Wolfgang Tichy]

Package: src:linux
Version: 3.16.7-ckt25-2+deb8u3
Severity: critical
Tags: security
Justification: causes serious data loss

Dear Maintainer,

when I open a particular word document (it contains images and I can send it
to you for testing) with libreoffice, all memory and all swap get used up
within about a minute. This happens slowly enough that it can be monitored
with "top" and "free". What I see with top is that soffice.bin (which is
libreoffice) does not use much memory (maybe 2%). Nevertheless more and more
memory gets used. "free -h" gives something like this:

 total   used   free sharedbuffers cached
Mem:  7.5G   7.4G   141M   5.9G71M   6.4G
-/+ buffers/cache:   917M   6.6G
Swap: 8.0G   663M   7.4G

Eventually the "used" column in the "Mem:" and "Swap:" and lines reach the
total and the system runs out of memory and becomes totally unresponsive
(even the mouse pointer freezes), no remote logins are possible at this
point, and all keypresses are ignored. The only way to regain control is by
holding down the power button for 10s. However, the "used" column in the
"-/+ buffers/cache:" line stays near 1GB, so that it is clear that
buffers/caches take up almost all the space.

You may wonder why I file this against the kernel and not libreoffice. Well,
I am sure libreoffice is doing something stupid, that could be fixed to
circumvent this problem. But the kernel should simply not allow any user
process to bring down the entire system. Also it seems the kernel is
allocating caches or buffers until it runs out of all memory and then
freezes. If it was only libreoffice allocating memory, OOM killer would kill
it. But nothing like this happens, even if you wait 2h nothing happens. I
think OOM killer does nothing because no single user process uses a lot of
memory. It's the kernel choking on itself. 

Ok, so now let me speculate on what might be wrong. I am filing this report
for my laptop that has a i7-3667U CPU with integrated Intel graphics card:
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
But the problem also occurs on 3 other Debian desktop machines that run the
same kernel, and have either Intel or ATI graphics, i.e.:
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen 
Core Processor Integrated Graphics Controller (rev 06)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Barts 
PRO [Radeon HD 6850]
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]
However, it happens differently on a 4th Debian desktop machine with
07:00.0 VGA compatible controller: NVIDIA Corporation NV42GL [Quadro FX 
3450/4000 SDI] (rev a2)
On this one, Gnome3 crashes and dmesg has a lot of lines lines like:
[880754.926611] [TTM] Failed to find memory space for buffer 0x880367e42800 
eviction
[880754.926613] [TTM] No space for 880367e42800 (497 pages, 1988K, 1M)
[880754.926614] [TTM]   placement[0]=0x00070002 (1)
[880754.926616] [TTM] has_type: 1
[880754.926617] [TTM] use_type: 1
[880754.926618] [TTM] flags: 0x000A
[880754.926619] [TTM] gpu_offset: 0x
[880754.926620] [TTM] size: 131072
[880754.926621] [TTM] available_caching: 0x0007
[880754.926622] [TTM] default_caching: 0x0001
This is actually good because after the gnome3 crash the system is still
usable. I should say that in all cases I am using the open source graphics
drivers that use kernel mode setting. So the latter crash leads me to think
that some interaction between the graphics drivers and the kernel leads to
the allocation of too many buffers/caches by the kernel until it runs out.
Probably this is all triggered by libreoffice (running on X) trying to
display some JPG images in a document.

The reason why I consider this security relevant is that anybody with a user
account can use libreoffice to bring the system down. This will cause data
loss since all other users cannot save any data in open files.

Thank you very much for considering this report,
Wolfgang Tichy


-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=111acff4-4673-47ad-85a1-43f48c1c7621 ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[44950.827165] Broke affinity for irq 41
[44950.930086] smpboot: CPU 3 is now offline
[44950.931077] PM: Creating hibernation image:
[44951.233670] PM: Need to copy 785394 pages
[44951.233677] PM: Normal pages needed: 785394 + 1024, available pages: 1234019
[44950.933557] PM: Restoring platform NVS memory
[44950.934317] Enabling non-boot CPUs ...
[44950.934528] x86: Booting SMP configuration:
[44950.934531] smpboot: Booting Node 

Bug#837121: marked as done (gazebo: please restrict libkido-dev (build-)dependency to architectures where it is available.)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 19:33:58 +
with message-id 
and subject line Bug#837121: fixed in gazebo 7.3.0+dfsg-4
has caused the Debian Bug report #837121,
regarding gazebo: please restrict libkido-dev (build-)dependency to 
architectures where it is available.
to be marked as done.

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

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


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

Package: gazebo
Version: 7.3.0+dfsg-3
Severity: serious
Tags: patch

The most recent version of gazebo added a build-dependency on 
libkido-dev to the source package and added a binary on libkido-dev to 
libgazebo7-dev


No mention of this was made in the changelog and no other changes in the 
upload seem to be related but 
https://anonscm.debian.org/git/debian-science/packages/gazebo.git/commit/?id=80f9a218ccebb32258812afdf1cce6b50ab88126 
indicates this was to add support for a new feature.


libkido-dev is only available on a handful of architectures. As a result 
this new (build-)dependency is blocking the migration of the new version 
of the package (and hence the FTBFS fix) to testing.


The attatched patch restricts the (build-)dependencies on libkido-dev to 
the architectures where it is actually available (amd64, arm64, i386, 
ppc64el and alpha)
diff -Nru gazebo-7.3.0+dfsg/debian/changelog gazebo-7.3.0+dfsg/debian/changelog
--- gazebo-7.3.0+dfsg/debian/changelog  2016-08-31 17:57:53.0 +
+++ gazebo-7.3.0+dfsg/debian/changelog  2016-09-07 15:06:23.0 +
@@ -1,3 +1,10 @@
+gazebo (7.3.0+dfsg-3+rpi1) stretch-staging; urgency=medium
+
+  * Restrict (build-)dependency on libkido-dev to architectures where that 
package
+is actually available (amd64, arm64, i386, ppc64el and alpha). 
+
+ -- Peter Michael Green   Wed, 07 Sep 2016 15:06:23 
+
+
 gazebo (7.3.0+dfsg-3) unstable; urgency=medium
 
   [ Jochen Sprickerhof ]
diff -Nru gazebo-7.3.0+dfsg/debian/control gazebo-7.3.0+dfsg/debian/control
--- gazebo-7.3.0+dfsg/debian/control2016-08-30 22:54:59.0 +
+++ gazebo-7.3.0+dfsg/debian/control2016-09-07 15:06:07.0 +
@@ -45,7 +45,7 @@
libbullet-dev,
libsimbody-dev,
libsimbody-dev (<< 4.0.0),
-   libkido-dev,
+   libkido-dev [amd64 arm64 i386 powerpc alpha],
libgdal-dev,
ruby-ronn,
libgtest-dev
@@ -138,7 +138,7 @@
  libignition-math2-dev,
  libbullet-dev,
  libsimbody-dev,
- libkido-dev,
+ libkido-dev [amd64 arm64 i386 powerpc alpha],
  libgazebo7 (= ${binary:Version}),
  gazebo7-common (= ${source:Version}),
  gazebo7-plugin-base (= ${binary:Version}),
--- End Message ---
--- Begin Message ---
Source: gazebo
Source-Version: 7.3.0+dfsg-4

We believe that the bug you reported is fixed in the latest version of
gazebo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated gazebo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Fri, 09 Sep 2016 21:21:16 +0200
Source: gazebo
Binary: gazebo7-common gazebo7 libgazebo7 libgazebo7-dev gazebo7-plugin-base 
gazebo7-doc
Architecture: source
Version: 7.3.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 gazebo7- Open Source Robotics Simulator - Binaries
 gazebo7-common - Open Source Robotics Simulator - Shared files
 gazebo7-doc - Open Source Robotics Simulator - Documentation
 gazebo7-plugin-base - Open Source Robotics Simulator - base plug-ins
 libgazebo7 - Open Source Robotics Simulator - shared library
 libgazebo7-dev - Open Source Robotics Simulator - Development Files
Closes: 837121
Changes:
 gazebo (7.3.0+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Peter Michael 

Bug#810709: marked as done (yt: FTBFS: TypeError: can't pickle Cython.Compiler.FlowControl.NameAssignment objects)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 19:07:40 +
with message-id 
and subject line Bug#810709: fixed in yt 3.2.3-1
has caused the Debian Bug report #810709,
regarding yt: FTBFS: TypeError: can't pickle 
Cython.Compiler.FlowControl.NameAssignment objects
to be marked as done.

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

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


-- 
810709: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yt
Version: 3.2.1-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,

yt fails to build from source in unstable/amd64:

  [..]

  I: pybuild base:184: /usr/bin/python3.5 setup.py build 
  non-existing path in 'yt/utilities/spatial': 'yt/utilities/spatial/tests'
  running build
  running config_cc
  unifing config_cc, config, build_clib, build_ext, build commands --compiler 
options
  running config_fc
  unifing config_fc, config, build_clib, build_ext, build commands --fcompiler 
options
  running build_src
  build_src
  building py_modules sources
  creating build/src.linux-x86_64-3.5
  creating build/src.linux-x86_64-3.5/yt
  creating build/src.linux-x86_64-3.5/yt/analysis_modules
  creating 
build/src.linux-x86_64-3.5/yt/analysis_modules/cosmological_observation
  creating 
build/src.linux-x86_64-3.5/yt/analysis_modules/cosmological_observation/light_cone
  creating 
build/src.linux-x86_64-3.5/yt/analysis_modules/cosmological_observation/light_ray
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/halo_finding
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/halo_finding/fof
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/halo_finding/hop
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/halo_mass_function
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/level_sets
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/particle_trajectories
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/photon_simulator
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/spectral_integrator
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/star_analysis
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/two_point_functions
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/sunyaev_zeldovich
  creating build/src.linux-x86_64-3.5/yt/analysis_modules/ppv_cube
  creating build/src.linux-x86_64-3.5/yt/data_objects
  creating build/src.linux-x86_64-3.5/yt/fields
  creating build/src.linux-x86_64-3.5/yt/extern
  creating build/src.linux-x86_64-3.5/yt/frontends
  creating build/src.linux-x86_64-3.5/yt/frontends/art
  creating build/src.linux-x86_64-3.5/yt/frontends/artio
  creating build/src.linux-x86_64-3.5/yt/frontends/athena
  creating build/src.linux-x86_64-3.5/yt/frontends/boxlib
  creating build/src.linux-x86_64-3.5/yt/frontends/chombo
  creating build/src.linux-x86_64-3.5/yt/frontends/eagle
  creating build/src.linux-x86_64-3.5/yt/frontends/enzo
  creating build/src.linux-x86_64-3.5/yt/frontends/fits
  creating build/src.linux-x86_64-3.5/yt/frontends/flash
  creating build/src.linux-x86_64-3.5/yt/frontends/gadget
  creating build/src.linux-x86_64-3.5/yt/frontends/gadget_fof
  creating build/src.linux-x86_64-3.5/yt/frontends/gdf
  creating build/src.linux-x86_64-3.5/yt/frontends/halo_catalog
  creating build/src.linux-x86_64-3.5/yt/frontends/http_stream
  creating build/src.linux-x86_64-3.5/yt/frontends/moab
  creating build/src.linux-x86_64-3.5/yt/frontends/owls
  creating build/src.linux-x86_64-3.5/yt/frontends/owls_subfind
  creating build/src.linux-x86_64-3.5/yt/frontends/ramses
  creating build/src.linux-x86_64-3.5/yt/frontends/rockstar
  creating build/src.linux-x86_64-3.5/yt/frontends/sdf
  creating build/src.linux-x86_64-3.5/yt/frontends/sph
  creating build/src.linux-x86_64-3.5/yt/frontends/stream
  creating build/src.linux-x86_64-3.5/yt/frontends/tipsy
  creating build/src.linux-x86_64-3.5/yt/geometry
  creating build/src.linux-x86_64-3.5/yt/gui
  creating build/src.linux-x86_64-3.5/yt/units
  creating build/src.linux-x86_64-3.5/yt/utilities
  creating build/src.linux-x86_64-3.5/yt/utilities/answer_testing
  creating build/src.linux-x86_64-3.5/yt/utilities/grid_data_format
  creating build/src.linux-x86_64-3.5/yt/utilities/grid_data_format/conversion
  creating build/src.linux-x86_64-3.5/yt/utilities/lib
  creating build/src.linux-x86_64-3.5/yt/visualization
  creating 

Bug#836824: python-pyotp: FTBFS in testing (failing tests)

[Hugo Lefeuvre]

Hi Santiago,

It looks like packaging the new upstream release fixes the issue.
If you want, you can try to build the version on the repository[0]
before I upload it.

Regards,
 Hugo

[0] https://anonscm.debian.org/git/python-modules/packages/python-pyotp.git/

-- 
 Hugo Lefeuvre (hle)|www.owl.eu.com
4096/ ACB7 B67F 197F 9B32 1533 431C AC90 AC3E C524 065E


signature.asc
Description: PGP signature

Bug#827655: marked as done (quodlibet: FTBFS: Theme error: sphinx_rtd_theme is no longer a hard dependency since version 1.4.0. Please install it manually)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 17:31:07 +
with message-id 

Bug#797526: marked as done (mapsembler2: FTBFS with GCC-5 - undefined reference to `prefix_trashable[abi:cxx11]')

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 16:42:57 +
with message-id 
and subject line Bug#797526: fixed in mapsembler2 2.2.3+dfsg-3
has caused the Debian Bug report #797526,
regarding mapsembler2: FTBFS with GCC-5 - undefined reference to 
`prefix_trashable[abi:cxx11]'
to be marked as done.

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

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


-- 
797526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mapsembler2
Version: 2.2.3+dfsg-2
Severity: serious
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

During a rebuild against GCC-5 mapsembler2 FTBFS with:

/tmp/ccXWIZkS.o: In function `main':
/«BUILDDIR»/mapsembler2-2.2.3+dfsg/mapsembler2_extend/mapsembler_extend.cpp:320:
 undefined reference to `prefix_trashable[abi:cxx11]'
collect2: error: ld returned 1 exit status
make[2]: *** [mapsembler_extend] Error 1
makefile:113: recipe for target 'mapsembler_extend' failed
make[2]: Leaving directory 
'/«BUILDDIR»/mapsembler2-2.2.3+dfsg/mapsembler2_extend'
make[1]: *** [override_dh_auto_build] Error 2
debian/rules:27: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory '/«BUILDDIR»/mapsembler2-2.2.3+dfsg'
make: *** [build] Error 2
debian/rules:21: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Full build log on request.

Thanks,

_g.

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJV5DJpAAoJEO/obGx//s+DCHUIAIDi4dIxSFsK96zlMbDjXjvQ
vSUOz/wkMt6PS/+NFZ6lAsjUQnuviZVl/le9fgnGP99CHYT+UAxshE2af46w5MZq
R+SMfdGCbGLMO2NhXtiaSMk5ooWKpn+Rk2WKLZQ2rT5B++G0MiXlc3u/i0YcKBsJ
fmNgUELLQKInZt2OvKTO/qO5CrQOhBaZvAWD94sxv5w988MEhrk0DVHbERrdfZ1C
K1nHkl9APNM4P+EXCfHxgfR1HKbCwIUhDntnzQduPOD3b/vBNPFUzUcFyH9C+ghh
ZCs8nQETxEr9Yt9wr2z/90Lgvtubbi8CxowAQ2dbJALzll8QFp1OB63r2vwqM4U=
=1W/8
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: mapsembler2
Source-Version: 2.2.3+dfsg-3

We believe that the bug you reported is fixed in the latest version of
mapsembler2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 797...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated mapsembler2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Sep 2016 15:41:22 +0200
Source: mapsembler2
Binary: mapsembler2
Architecture: source amd64
Version: 2.2.3+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 mapsembler2 - bioinformatics targeted assembly software
Closes: 797526
Changes:
 mapsembler2 (2.2.3+dfsg-3) unstable; urgency=medium
 .
   * Fix type of prefix_trashable since gcc-5 is picky about it (Thanks to
 Gianfranco Costamagna  for the hint)
 Closes: #797526
   * cme fix dpkg-control
   * DEP5 syntax
   * hardening=+all
 .
   [ Olivier Sallou ]
   * d/copyright: add Upstream-Contact
Checksums-Sha1:
 c77f0a3afbaf0d4c12673c19ff477d4bc2a76f19 2287 mapsembler2_2.2.3+dfsg-3.dsc
 7fb1761e1d3e472e1f4047c58f1de1f323057ead 8920 
mapsembler2_2.2.3+dfsg-3.debian.tar.xz
 0e5b59085578e8233a0c61267bc1a56208d180b4 2182224 
mapsembler2-dbgsym_2.2.3+dfsg-3_amd64.deb
 e7b96a60bf0d53ff0adeceeaad75307f34153714 249118 
mapsembler2_2.2.3+dfsg-3_amd64.deb
Checksums-Sha256:
 ff977f20eac84e25b3bff28ed0e405d035f84873abfa02464bf0ca515fa690fa 2287 
mapsembler2_2.2.3+dfsg-3.dsc
 10864696c04e708a5e21b323eb78b421d2831f20f00cd9f233d3a5e377075156 8920 
mapsembler2_2.2.3+dfsg-3.debian.tar.xz
 3c05e9d2b8b9b87fcf59bd38f1883735af7a1f611c6d926da173f3e5cee8c6c2 

Bug#837152: marked as done (armadillo: Dependencies not satisfiable (superlu updated to 5.2.1))

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 16:35:04 +
with message-id 
and subject line Bug#837152: fixed in armadillo 1:7.400.1+dfsg-2
has caused the Debian Bug report #837152,
regarding armadillo: Dependencies not satisfiable (superlu updated to 5.2.1)
to be marked as done.

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

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


-- 
837152: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: armadillo
Version: 1:6.700.6+dfsg-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:qgis src:gdal src:pktools src:vtk6

Dear Maintainer,

superlu has been updated to version 5.2.1 in unstable, which makes
the armadillo packages uninstallable due to the version 4.3 constraint.

This affects all reverse dependencies of armadillo.

Version 1:7.400.1+dfsg-1 in experimental does not have the superlu 4.3
version constraint, but will require a transition. Please coordinate the
armadillo transition with the Release Team as soon as possible, or fix
the superlu dependency issue for the version in unstable in the mean
time.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: armadillo
Source-Version: 1:7.400.1+dfsg-2

We believe that the bug you reported is fixed in the latest version of
armadillo, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kumar Appaiah  (supplier of updated armadillo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Sep 2016 20:56:23 +0530
Source: armadillo
Binary: libarmadillo-dev libarmadillo7
Architecture: source amd64
Version: 1:7.400.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Kumar Appaiah 
Description:
 libarmadillo-dev - streamlined C++ linear algebra library - Headers
 libarmadillo7 - streamlined C++ linear algebra library
Closes: 837152
Changes:
 armadillo (1:7.400.1+dfsg-2) unstable; urgency=medium
 .
   * Upload to unstable
   * Works with superlu 5 (Closes: #837152)
Checksums-Sha1:
 29100968b5fdff186986a55dc6bdcc3a38070e0f 2155 armadillo_7.400.1+dfsg-2.dsc
 ba73e15811972e7de04a2f1a64d2bff66b2dcff5 11244 
armadillo_7.400.1+dfsg-2.debian.tar.xz
 6343a849423ad9ab57a10f09cf5ec3934f23ad55 319468 
libarmadillo-dev_7.400.1+dfsg-2_amd64.deb
 eab84d589653eb35723394bfff645d2f6999a544 37838 
libarmadillo7-dbgsym_7.400.1+dfsg-2_amd64.deb
 65a35931cfd20f16e59c14fc4c2dc96742187b7d 81180 
libarmadillo7_7.400.1+dfsg-2_amd64.deb
Checksums-Sha256:
 9c366cb3a247b647fbebc7ad6a4f5ba8222f2cf85ac3c76492c79e542387f887 2155 
armadillo_7.400.1+dfsg-2.dsc
 d4cd66b70b69f8348878132efea27b922dc1901c8a4251a0597286208a05eed3 11244 
armadillo_7.400.1+dfsg-2.debian.tar.xz
 bfcee976b5e61eaf0ff9c6817ade214da8637f9cdba0123eca3f8d2f1f8b6521 319468 
libarmadillo-dev_7.400.1+dfsg-2_amd64.deb
 ceac0c268796d349ac7617a0436b138f2a5542339706c31551cf3238f1d94bb4 37838 
libarmadillo7-dbgsym_7.400.1+dfsg-2_amd64.deb
 8c8e2c3d97305a3279e1eaf2b1b86acec0625fe9f90902ec1f8702bec9346272 81180 
libarmadillo7_7.400.1+dfsg-2_amd64.deb
Files:
 0f26b4de44ca91683bf2c734986ade06 2155 libs optional 
armadillo_7.400.1+dfsg-2.dsc
 35864e4e38486cd129feaa72b8f53e50 11244 libs optional 
armadillo_7.400.1+dfsg-2.debian.tar.xz
 f6b09e2efc93554497cc51dab47ac518 319468 libdevel optional 
libarmadillo-dev_7.400.1+dfsg-2_amd64.deb
 7223da36288b54e2fc7972d204666ec9 37838 debug extra 
libarmadillo7-dbgsym_7.400.1+dfsg-2_amd64.deb
 43c58e9422ec1fe6d1d723c045c101ce 81180 libs optional 
libarmadillo7_7.400.1+dfsg-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX0t4fAAoJEHqPSei2NIC+46QQAIWfRfskD6MAhnecF188ezOa
4Lo3Of674KBJLw5H7XNOjeoQhhb8krEg0y9aCEPVnVX+nG+bMe+BXgTAH1/3zGPg
ba1sHdESJBgvdf5iud6axoYRCkXbXdtu5mBufgQ1DomjZXSc624K+JBtQIGH21t1
j4uo7PIxj+tm4enYXZhhuQ2WjjnFRfD1NgHeeunYLzTdbuTYb8ToocLV9zsH0Azd
s2OuSguyoRXnaLe/lE+Xr56YRMmMALR/e9Anmq8ozSz1ZYKmqnCWoj1wg0+dMcHq

Bug#808312: marked as done (chemps2: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man1/chemps2.1.gz)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 16:35:28 +
with message-id 
and subject line Bug#808312: fixed in chemps2 1.8-2
has caused the Debian Bug report #808312,
regarding chemps2: fails to upgrade from 'testing' - trying to overwrite 
/usr/share/man/man1/chemps2.1.gz
to be marked as done.

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

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


-- 
808312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chemps2
Version: 1.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Preparing to unpack .../chemps2_1.6-2_amd64.deb ...
  Unpacking chemps2 (1.6-2) over (1.6-1+b1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/chemps2_1.6-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/chemps2.1.gz', which is also in 
package libchemps2-1 1.6-1+b1
  Preparing to unpack .../libchemps2-1_1.6-2_amd64.deb ...
  Unpacking libchemps2-1 (1.6-2) over (1.6-1+b1) ...
  Processing triggers for libc-bin (2.21-4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/chemps2_1.6-2_amd64.deb


cheers,

Andreas


chemps2_1.6-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: chemps2
Source-Version: 1.8-2

We believe that the bug you reported is fixed in the latest version of
chemps2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 808...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Wouters  (supplier of updated chemps2 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 08 Sep 2016 21:58:29 +0200
Source: chemps2
Binary: libchemps2-2 libchemps2-dev chemps2-doc chemps2 python-chemps2
Architecture: source
Version: 1.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Sebastian Wouters 
Description:
 chemps2- Executable to call libchemps2-2 from the command line
 chemps2-doc - Documentation of the libchemps2-2 package
 libchemps2-2 - Spin-adapted DMRG for ab initio quantum chemistry
 libchemps2-dev - C++ headers, static library, and symlink for libchemps2-2
 python-chemps2 - Python 2 interface for libchemps2-2
Closes: 808312
Changes:
 chemps2 (1.8-2) unstable; urgency=medium
 .
* Fix overwriting chemps2.1.gz libchemps2-1 (Closes: #808312)
Checksums-Sha1:
 67df05e7eac6a4895379f0e96a2c875bd2f6ab92 2430 chemps2_1.8-2.dsc
 aad1bc1842cfe0f5ba25e466d8ca020161e1069d 12904 chemps2_1.8-2.debian.tar.xz
Checksums-Sha256:
 970cf2b1f5b47a934aa01c8b9c739f4655f6f980554bdbecf730066109e5d574 2430 
chemps2_1.8-2.dsc
 33aa89ba9ab1530331d6b04b1af81a6db200d7a74f02f380881fd188697f1aef 12904 
chemps2_1.8-2.debian.tar.xz
Files:
 36d37525cdbcb9bfa718716be70df344 2430 libs optional chemps2_1.8-2.dsc
 1e1e2dad1e7d3ca574dea613ca607a12 12904 libs optional 
chemps2_1.8-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJX0r+3AAoJEK/P7I5mnOHCjE8P/2FPoueceGXKo6y/yfYMWq3u
mzs+MpX0B9w+Kn079rFq0iBt0uytAx94dxZNipiVdwj0oWdv2ZlDqfVN0+KzT0qf
uTrBkJHBAsfN2iZKmC/MfEFr6yxPETAVYhVV98MDuN21jUA8MhzPcTfv4RSp/sQD
19YJU+B2DwPNpG+YNpknjSf3w/RZ5RsE9iz8ePF5a8crSgzXdc4gxHRtJmunDVjM
WBdr1H1aheU3JvBXBisWiP/2f0iQH2MGzB5ezfVU9M+q6eZg7fVP4aRTRkKy3JLk
3z75SsoxPJGgoD7AmRjprnl5XPYL8h9DscJSKMxxJ/Ng67UDFRBKo63NRK//WYLA
QQeWo3PVDl+hkcBfTcBfIjwwTJiz4of5iWD17Yb/8uGjOQFkgd2qui9Op3BT4EBB
wsQcWI+xxw7rGnVWK2j0rl0WQuWELE84ob9fH4dp9lJXpm39+O//33s7qjyt6SMh
Oy62biAE0QyCZvCwojGImxWsSCV/CeKBkE4ak1+QqqJPypeokkRdh4vCguJgO9Vf
WrrsNlDb42yB+3YQ7EmsdxiNggcYJymii7eBiNgnXovKFv+5ifz6efjKpnh0K7Q4
dwf35tw92m/QCmhJye5i/P5qk5L1bVKkwwIAYySc5l9Y+0QQLIcmqD/13QgAZS5y

Bug#817443: marked as done (easyh10: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 16:36:01 +
with message-id 
and subject line Bug#817443: fixed in easyh10 1.5-2
has caused the Debian Bug report #817443,
regarding easyh10: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: easyh10
Severity: important
Usertags: compat-4-removal

Hi,

The package easyh10 uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: easyh10
Source-Version: 1.5-2

We believe that the bug you reported is fixed in the latest version of
easyh10, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Allan Dixon Jr.  (supplier of updated easyh10 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 16:41:57 -0300
Source: easyh10
Binary: easyh10
Architecture: source
Version: 1.5-2
Distribution: unstable
Urgency: medium
Maintainer: Allan Dixon Jr. 
Changed-By: Allan Dixon Jr. 
Description:
 easyh10- Utility to manage the iRiver H10 music player
Closes: 615401 760136 817443
Changes:
 easyh10 (1.5-2) unstable; urgency=medium
 .
   * New maintainer. (Closes: #760136)
   * Add a break line in debian/README.Debian.
   * Add the Homepage field in debian/control. (Closes: #615401)
   * Bump Standards-Version to 3.9.8.
   * Change DH to 9. (Closes: #817443)
   * Fix the Section in debian/menu file.
   * Migrate debian/rules format and using full hardening variables.
   * New format to debian/copyright (1.0).
   * Patches to fix configure.in and Makefile.am.
   * Patch to fix spelling errors.
   * Priority from extra to optional in debian/control.
   * Switch to dpkg-source 3.0 (quilt) format.
   * Using a watch file with version 4. Thanks to bartm.
Checksums-Sha1:
 b49e09a0e4d27de3255eda4a82bf3a79cd53bfc0 1677 easyh10_1.5-2.dsc
 d5c0d16e2390370b82bde8402249e681c4ea2d56 6020 easyh10_1.5-2.debian.tar.xz
Checksums-Sha256:
 06ff3273dac91c0206e0bb8fa3a27294b09b51b2d4e4e217c45743bcd0bf5dfe 1677 
easyh10_1.5-2.dsc
 3f8f947eb85274aecc74f7c1cfe0a332f46852992d780dc40be09ae977b8ac57 6020 
easyh10_1.5-2.debian.tar.xz
Files:
 65e526d71b1c20ea8e1d6c97aedd85bb 1677 sound optional easyh10_1.5-2.dsc
 27a408411fabeb1995103eefa8bdab02 6020 sound optional 
easyh10_1.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX0sAxAAoJEN5juccE6+nvJXUP/jCC4ALP7erp6mMWGjXHdMJZ
qGmBQR3PdMcWkpBGCEQLnyiqHAvEDGKZc41YnBU96bPYkcDuAZz80JdBEig3+DyG
fBmTKFgD9UiAkmnUBiAmoJXBpkGVv/GJsYG4FDPcQ9AknDWDIuFpCtNkIhtIG6Qi
D61fWMy85SpJDeHepLv/vt6JNyHbzNRfbf0WxTykrTnUXUcaIEmV+//v6MWhw2jj
FAQJbAIEKzK0YQycdvG4B72yxfw6lqLc9aFCttrpJG7iYE7+V768H6HQNVqMd5Us
xL67yfxA0FrJx/SbiAN9Gg+mkbEAKB4YCGEW6lDxx2geudhYd2TmbDfc4uRJabae
+Ec8GYb0uD6eFj5R/AlpIeU7lf1fB5RqoLt/z41RRb750L78cSLVq6jMuILo/cmu
cQddQp0UNZHVBP+iqlTrsKUDC8LOaL3MhKYpWxUxIplItk0UVmbgiPg4CLGHQJ7d
jcM1NtWjxPD6nJtFZuhACoUHI71GwEs2bfQFJJ06CHTc2UVzbCNx82drkwFgyaCo
kiCQtgyxgmDbkCxqYfy4Dn0qLuh39DqglmWP0wBPwcmfUi7gDlTu+fUYJmNGmKeu
QHcrwskvF/WrqAbOqXAaQvsDwybk0eNEunYBj3uGClHF6hxzeerK/I2sFFU3EgzC
y2AyX6zUkH+FpCT3T5Gp
=artP
-END PGP SIGNATURE End Message ---

Bug#835185: mysql-workbench: Segfault when opening connection

[Maurizio Avogadro]

The culprit seems to be libmysqlcppconn7v5: v1.1.4+really1.1.3-1 from
Sid seems to fix the issue.

Please merge this bug report with #836587.

Processed: limit source to armadillo, tagging 837152

[Debian Bug Tracking System]

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

> limit source armadillo
Limiting to bugs with field 'source' containing at least one of 'armadillo'
Limit currently set to 'source':'armadillo'

> tags 837152 + pending
Bug #837152 [src:armadillo] armadillo: Dependencies not satisfiable (superlu 
updated to 5.2.1)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#802412: seaborn: FTBFS: FAIL: seaborn.tests.test_matrix.TestDendrogram.test_dendrogram_ticklabel_rotation

[Sandro Tosi]

for the first and third there is
https://github.com/mwaskom/seaborn/issues/836 which seems to be
addressed using Agg matplotlib backend but there is no issue for the
second failure

would be great to get this package back in stable, let me know if help is needed

Processed: bug 835684 is forwarded to https://github.com/syncthing/syncthing/issues/3533

[Debian Bug Tracking System]

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

> forwarded 835684 https://github.com/syncthing/syncthing/issues/3533
Bug #835684 [src:syncthing] syncthing: FTBFS: dh_auto_test: go test -v -p 1 
github.com/syncthing/syncthing/cmd/stbench 
github.com/syncthing/syncthing/cmd/stcompdirs 
github.com/syncthing/syncthing/cmd/stdisco 
github.com/syncthing/syncthing/cmd/stdiscosrv 
github.com/syncthing/syncthing/cmd/stevents 
github.com/syncthing/syncthing/cmd/stfileinfo 
github.com/syncthing/syncthing/cmd/stfinddevice 
github.com/syncthing/syncthing/cmd/stgenfiles 
github.com/syncthing/syncthing/cmd/stindex 
github.com/syncthing/syncthing/cmd/strelaysrv 
github.com/syncthing/syncthing/cmd/strelaysrv/testutil 
github.com/syncthing/syncthing/cmd/stsigtool 
github.com/syncthing/syncthing/cmd/stvanity 
github.com/syncthing/syncthing/cmd/stwatchfile 
github.com/syncthing/syncthing/cmd/syncthing 
github.com/syncthing/syncthing/lib/auto 
github.com/syncthing/syncthing/lib/beacon 
github.com/syncthing/syncthing/lib/config 
github.com/syncthing/syncthing/lib/connections 
github.com/syncthing/syncthing/lib/db github.com/syncthing/syncthing/lib/dialer 
github.com/syncthing/syncthing/lib/discover 
github.com/syncthing/syncthing/lib/events github.com/syncthing/syncthing/lib/fs 
github.com/syncthing/syncthing/lib/ignore 
github.com/syncthing/syncthing/lib/logger 
github.com/syncthing/syncthing/lib/model github.com/syncthing/syncthing/lib/nat 
github.com/syncthing/syncthing/lib/osutil 
github.com/syncthing/syncthing/lib/pmp 
github.com/syncthing/syncthing/lib/protocol 
github.com/syncthing/syncthing/lib/rand github.com/syncthing/syncthing/lib/rc 
github.com/syncthing/syncthing/lib/relay/client 
github.com/syncthing/syncthing/lib/relay/protocol 
github.com/syncthing/syncthing/lib/scanner 
github.com/syncthing/syncthing/lib/signature 
github.com/syncthing/syncthing/lib/stats 
github.com/syncthing/syncthing/lib/symlinks 
github.com/syncthing/syncthing/lib/sync 
github.com/syncthing/syncthing/lib/tlsutil 
github.com/syncthing/syncthing/lib/upgrade 
github.com/syncthing/syncthing/lib/upnp github.com/syncthing/syncthing/lib/util 
github.com/syncthing/syncthing/lib/versioner returned exit code 1
Set Bug forwarded-to-address to 
'https://github.com/syncthing/syncthing/issues/3533'.
> thanks
Stopping processing here.

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

Bug#834180: marked as pending

[Herbert Parentes Fortes Neto]

tag 834180 pending
thanks

Hello,

Bug #834180 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-multimedia/bristol.git;a=commitdiff;h=681da27

---
commit 681da27e9edec0abd74ef150aede33a36bab63d1
Author: Herbert Parentes Fortes Neto 
Date:   Fri Sep 9 09:04:38 2016 -0300

Import Debian patch 0.60.11-3

diff --git a/debian/changelog b/debian/changelog
index 0e629f9..d993c3b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+bristol (0.60.11-3) unstable; urgency=medium
+
+  * Team upload.
+  * debian/copyright:
+  - Put my name in 'Files: debian/*' entry.
+  * debian/patches:
+  - 03-rm_alsa-iatomic.h.patch added. (Closes: #834180)
+Thanks Adrian Bunk and James Cowgill.
+
+ -- Herbert Parentes Fortes Neto   Fri, 09 Sep 2016 09:04:38 
-0300
+
 bristol (0.60.11-2) unstable; urgency=low
 
   * Upload to unstable.

Processed: Bug#834180 marked as pending

[Debian Bug Tracking System]

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

> tag 834180 pending
Bug #834180 {Done: Herbert Parentes Fortes Neto } 
[src:bristol] bristol: FTBFS: audioEngineJack.c:42:26: fatal error: 
alsa/iatomic.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#825121: changed severity

[Raphael Hertzog]

Hi,

On Sat, 06 Aug 2016, Daniel Pocock wrote:
> Based on that feedback, I've raised the severity again, but I won't have
> time to start trying to code a solution for at least another 2 or 3
> weeks, has anybody seen any code in any other preinst / postinst that
> can be copied for this purpose?
> 
> If anybody else wants to try uploading a fix for this it would be very
> welcome, please just put a note in the bug if you start working on it.

I just uploaded an NMU that fixes this bug. The NMU patch is attached.

I was annoyed that the package got removed from testing as we use it in
Kali so I worked on it.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/
>From 3b1f47ce14848be18572233a79c23c7e785c7491 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rapha=C3=ABl=20Hertzog?= 
Date: Fri, 9 Sep 2016 16:03:54 +0200
Subject: [PATCH] Initialize /etc/radcli only with modified files from
 /etc/radiusclient/.

Properly install them after initial install from postinst to avoid prompt
during initial install. Handle the abort case as well.

Closes: #825121
---
 debian/changelog   |  9 +
 debian/libradcli4.postinst | 17 
 debian/libradcli4.postrm   | 12 +++
 debian/libradcli4.preinst  | 50 ++
 4 files changed, 71 insertions(+), 17 deletions(-)
 create mode 100644 debian/libradcli4.postinst
 create mode 100644 debian/libradcli4.postrm

diff --git a/debian/changelog b/debian/changelog
index 6fa461e..b9429dd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+radcli (1.2.6-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Initialize /etc/radcli only with modified files from /etc/radiusclient/.
+Properly install them after initial install from postinst to avoid prompt
+during initial install. Handle the abort case as well. Closes: #825121
+
+ -- Raphaël Hertzog   Fri, 09 Sep 2016 15:53:50 +0200
+
 radcli (1.2.6-2) unstable; urgency=high
 
   * preinst: update absolute directory paths in files from legacy client
diff --git a/debian/libradcli4.postinst b/debian/libradcli4.postinst
new file mode 100644
index 000..d5318a7
--- /dev/null
+++ b/debian/libradcli4.postinst
@@ -0,0 +1,17 @@
+#!/bin/sh
+
+set -e
+
+case $1 in
+configure)
+	for file in /etc/radcli/*.dpkg-migrated; do
+	if [ ! -e "$file" ]; then
+		continue
+	fi
+	echo "Overwriting ${file%%.dpkg-migrated} with original file from libfreeradius-client2"
+	mv $file ${file%%.dpkg-migrated}
+	done
+;;
+esac
+
+#DEBHELPER#
diff --git a/debian/libradcli4.postrm b/debian/libradcli4.postrm
new file mode 100644
index 000..e55f50a
--- /dev/null
+++ b/debian/libradcli4.postrm
@@ -0,0 +1,12 @@
+#!/bin/sh
+
+set -e
+
+case $1 in
+abort-install|abort-upgrade)
+	rm -f /etc/radcli/*.migrated
+	rmdir --ignore-fail-on-non-empty /etc/radcli
+;;
+esac
+
+#DEBHELPER#
diff --git a/debian/libradcli4.preinst b/debian/libradcli4.preinst
index a1f61eb..c854df3 100644
--- a/debian/libradcli4.preinst
+++ b/debian/libradcli4.preinst
@@ -1,23 +1,39 @@
 #!/bin/sh
+
 set -e
 
-if [ ! -d /etc/radcli ];
-then
-# no radcli config exists
+FILES_TO_MIGRATE="
+/etc/radiusclient/dictionary
+/etc/radiusclient/dictionary.ascend
+/etc/radiusclient/dictionary.compat
+/etc/radiusclient/dictionary.merit
+/etc/radiusclient/dictionary.sip
+/etc/radiusclient/radiusclient.conf
+/etc/radiusclient/servers
+"
 
-if [ -d /etc/radiusclient ];
-then
-# a legacy configuration from radiusclient-ng exists, use it,
-# as this package is a fork of radiusclient-ng
-echo "Using copy of existing /etc/radiusclient to initialize /etc/radcli"
-cp -ar /etc/radiusclient /etc/radcli
-for f in /etc/radcli/* ;
-do
-if [ -f "${f}" -a ! -h "${f}" ];
-then
-sed -i -e 's!/etc/radiusclient/!/etc/radcli/!g' "${f}"
-fi
-done
-fi
+is_modified_conffile() {
+actual_md5=$(md5sum $1 | awk '{print $1}')
+expected_md5=$(dpkg-query -f '${Conffiles}' -W libfreeradius-client2 | awk '$1 == "'"$1"'" { print $2 }')
+test "$actual_md5" != "$expected_md5"
+}
+
+if [ ! -d /etc/radcli ] && [ -d /etc/radiusclient ];
+then
+# no radcli config exists but a legacy configuration from
+# radiusclient-ng exists, use it, as this package is a fork of
+# radiusclient-ng
+mkdir -p /etc/radcli
+for file in $FILES_TO_MIGRATE; do
+	if is_modified_conffile $file; then
+	new_file="/etc/radcli/$(basename $file).dpkg-migrated"
+	echo "Preparing a copy of $file to initialize ${new_file%%.dpkg-migrated}"
+	cp -a $file $new_file
+if [ -f "$new_file" -a ! -h "$new_file" ]; then
+		sed -i -e 's!/etc/radiusclient/!/etc/radcli/!g' "$new_file"
+	fi
+	fi
+done
 fi
 
+#DEBHELPER#
-- 

Bug#802412: Could you please commit repository to git.debian.org if you want help

[Andreas Tille]

Hi Yaroslav,

I wanted to give #802412 a try since its blocking one of the Debian Med
tools from migrating to testing.  Unfortunately Vcs fields are wrong
(the repository does not exist at Github) and it should be rather on
alioth if you want team uploads.

Just for the record:  I tried to build seaborn 0.7.1 and was also
running into tast suite failures.  Did you contacted upstream about
this?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#837028: [Pkg-gauche-devel] Bug#837028: gauche-gtk: FTBFS: pango-font.c:249:44: error: 'desc' undeclared (first use in this function)

[Jens Thiele]

looks like the generated stub file (pango-font.stub) is already wrong:

;; pango_font_description_to_string
(define-cproc pango-font-description-to-string () "char *s = 
pango_font_description_to_string(desc);\n  ScmObj ss = SCM_MAKE_STR_COPYING(s\
);\n  g_free(s);\n  SCM_RETURN(ss);")

where it should be:
;; pango_font_description_to_string
(define-cproc pango-font-description-to-string (desc::) 
"char *s = pango_font_description_to_string(desc);\n  ScmObj ss = 
SCM_MAKE_STR_COPYING(s);\n  g_free(s);\n  SCM_RETURN(ss);")

later on pango-layout has a similar problem.
manually fixing those i still get an error:
gcc: error: pango-enum-types.o: No such file or directory

greetings,
jens

Processed: Tags pending

[Debian Bug Tracking System]

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

> tags 834170 pending
Bug #834170 [arb] arb: FTBFS with GCC 6
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: RE: linbox: FTBFS on mipsel (FAIL: test-charpoly)

[Debian Bug Tracking System]

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

> forwarded 797167 https://github.com/linbox-team/linbox/issues/37
Bug #797167 [src:linbox] linbox: FTBFS on mipsel (FAIL: test-charpoly)
Set Bug forwarded-to-address to 
'https://github.com/linbox-team/linbox/issues/37'.
> thanks
Stopping processing here.

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

Bug#837123: [anna] segfault in wheezy installer

[Aurelien Jarno]

On 2016-09-09 23:22, Vincent McIntyre wrote:
> On Fri, Sep 09, 2016 at 11:46:30AM +0200, Aurelien Jarno wrote:
> > Hi,
> > 
> > On 2016-09-09 10:27, Vincent McIntyre wrote:
> > > 
> > > Package: libc6-udeb
> > > Version: 2.13-38+deb7u10
> > > Severity: grave
> > > Justification: breaks installation entirely
> > > 
> > > The wheezy installer fails with anna reporting a segfault:
> > >
> > > ...
> > > anna[5033]: DEBUG: retrieving libc6-udeb 2.13-38+deb7u10
> > > anna[5033]: DEBUG: retrieving finish-install 2.41wheezy1
> > > anna[5033]: DEBUG: Segmentation fault
> > > anna[5033]: WARNING **: package retrieval failed
> > > kernel: [   66.427372] wget[5382]: segfault a 0 ip 7176c922c0ca sp 
> > > 7ffc8ca83890 error 6 in libresolv-2.13.so[7f76c9222000+13000]
> > > 
> > > This occurs shortly after libc6-udev is downloaded,
> > > according to the installer interactive display.
> > 
> > Unfortunately I am not able to reproduce the issue here. Given it
> > involves name resolving, I wouldn't be surprised it depends on the DNS
> > servers being used.
> 
> Seriously??? I have to use the exactly right flavour of DNS server?
> I think this would have been using microsoft DNS servers.
> I preseume you're using BIND?

I don't talk about the software running on your DNS servers, but rather
how they behave when they get queried. It might depends on many other
things, like if your network has IPv6 or not.

Note that's only one explanation, not sure it's the right one, but given
I am unable to reproduce the issue, it's the only one that come to my
mind.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#836589: fixed in icinga2 2.5.4-2

[Dejan Latinovic]

Hi,

Another solution could be to add ggc-min-expand=20 to CXXFLAGS.

The solution is tested on mips and mipsel.
A patch that contains needed changes is attached.

Regards,
Dejan





--- icinga2-2.5.4.orig/debian/rules	2016-08-26 08:11:01.0 +
+++ icinga2-2.5.4/debian/rules	2016-09-09 11:12:59.387685354 +
@@ -2,6 +2,13 @@
 
 #export DH_VERBOSE=1
 
+ 
+DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
+
+ifneq (,$(filter $(DEB_BUILD_ARCH),mips mipsel))
+	export DEB_CXXFLAGS_MAINT_APPEND = --param ggc-min-expand=20
+endif
+
 %:
 	dh $@ --with systemd --with bash_completion
 

Bug#837100: [PKG-Openstack-devel] Bug#837100: Bug#837100: Bug#837100: python-hacking dependency versions are pinned by upstream, package doesn't work with Debian ones

[James Page]

On Fri, 9 Sep 2016 at 14:33 Thomas Goirand  wrote:

> On 09/09/2016 12:38 AM, Víctor Cuadrado Juan wrote:
> > On Thu, 8 Sep 2016 23:35:27 +0200 Thomas Goirand 
> wrote:
> >> According to James Page, we should look into the Ubuntu package of
> >> hacking and get patches there to fix the issues.
> >
> > Why specifically the Ubuntu package, and not the Debian one?
>
> The latest Ubuntu package has the correct fixes, not the Debian one.
>

To be clear, the Ubuntu package has enough workarounds and hacks to allow
OpenStack packages for the Newton release to build - some of that enables
skipping of hacking tests as they just won't work with the newer
flake8/pycodestyle without some major refactoring, which I did not have
time todo.

Besides, if we're failing OpenStack builds on lint errors in Debian and
Ubuntu, we're probably about two steps to late as these should have been
caught in OpenStack gate already!

Bug#834685: marked as done (python-reno: FTBFS too much often (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 13:34:33 +
with message-id 
and subject line Bug#834685: fixed in python-reno 1.3.0-4
has caused the Debian Bug report #834685,
regarding python-reno: FTBFS too much often (failing tests)
to be marked as done.

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

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


-- 
834685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-reno
Version: 1.3.0-3
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=python_distutils 
--with python2,python3,sphinxdoc
dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: 
binary binary-arch binary-indep build build-arch build-indep clean install 
install-arch install-indep)
dh build-indep --buildsystem=python_distutils --with python2,python3,sphinxdoc
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions

[... snipped ...]

  File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory


==
FAIL: reno.tests.test_scanner.UniqueIdTest.test_modern
reno.tests.test_scanner.UniqueIdTest.test_modern
--
_StringException: Empty attachments:
  pythonlogging:''
  stderr
  stdout

Traceback (most recent call last):
  File "reno/tests/test_scanner.py", line 178, in setUp
self.useFixture(GPGKeyFixture())
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 679, in 
useFixture
reraise(*exc_info)
  File "/usr/lib/python2.7/dist-packages/testtools/testcase.py", line 666, in 
useFixture
fixture.setUp()
  File "reno/tests/test_scanner.py", line 67, in setUp
cwd=tempdir.path)
  File "reno/utils.py", line 44, in check_output
raw = subprocess.check_output(*args, **kwds)
  File "/usr/lib/python2.7/subprocess.py", line 567, in check_output
process = Popen(stdout=PIPE, *popenargs, **kwargs)
  File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
errread, errwrite)
  File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory


--
Ran 27 tests in 0.372s

FAILED (failures=22)
debian/rules:29: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:12: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-reno
Source-Version: 1.3.0-4

We believe that the bug you reported is fixed in the latest version of
python-reno, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  

Bug#837100: [PKG-Openstack-devel] Bug#837100: Bug#837100: python-hacking dependency versions are pinned by upstream, package doesn't work with Debian ones

[Thomas Goirand]

On 09/09/2016 12:38 AM, Víctor Cuadrado Juan wrote:
> On Thu, 8 Sep 2016 23:35:27 +0200 Thomas Goirand  wrote:
>> According to James Page, we should look into the Ubuntu package of
>> hacking and get patches there to fix the issues.
> 
> Why specifically the Ubuntu package, and not the Debian one?

The latest Ubuntu package has the correct fixes, not the Debian one.

Cheers,

Thomas Goirand (zigo)

Bug#837123: [anna] segfault in wheezy installer

[Vincent McIntyre]

On Fri, Sep 09, 2016 at 11:46:30AM +0200, Aurelien Jarno wrote:
> Hi,
> 
> On 2016-09-09 10:27, Vincent McIntyre wrote:
> > 
> > Package: libc6-udeb
> > Version: 2.13-38+deb7u10
> > Severity: grave
> > Justification: breaks installation entirely
> > 
> > The wheezy installer fails with anna reporting a segfault:
> >
> > ...
> > anna[5033]: DEBUG: retrieving libc6-udeb 2.13-38+deb7u10
> > anna[5033]: DEBUG: retrieving finish-install 2.41wheezy1
> > anna[5033]: DEBUG: Segmentation fault
> > anna[5033]: WARNING **: package retrieval failed
> > kernel: [   66.427372] wget[5382]: segfault a 0 ip 7176c922c0ca sp 
> > 7ffc8ca83890 error 6 in libresolv-2.13.so[7f76c9222000+13000]
> > 
> > This occurs shortly after libc6-udev is downloaded,
> > according to the installer interactive display.
> 
> Unfortunately I am not able to reproduce the issue here. Given it
> involves name resolving, I wouldn't be surprised it depends on the DNS
> servers being used.

Seriously??? I have to use the exactly right flavour of DNS server?
I think this would have been using microsoft DNS servers.
I preseume you're using BIND?

Could this be a locale thing?

> > The core of the issue is probably screwed up libc6 versions,
> > see bugs 740068, 833432
> 
> It indeeds looks like that, that said the build logs actually show
> that debian-installer 20130613+deb7u3+b2 has been built against
> glibc
> 2.13-38+deb7u10, so there is no version skew in this case.
> 
> Unfortunately, without being able to reproduce the problem, it
> will be very difficult to debug it.

Lovely. Thanks for bothering to reply.
Vince

Bug#802021: audacity: non-free files

[Herbert Fortes]

Hi,

On Wed, 7 Sep 2016 22:08:59 +0100 James Cowgill wrote:
> Hi,
>
> On 07/09/16 20:26, Herbert Fortes wrote:
> >>
> >> Files in "lib-src/libnyquist/nyquist/xlisp" have the following in the
> > header:
> >>
> >> Copyright (c) 1985, by David Michael Betz
> >> All Rights Reserved
> >> Permission is granted for unrestricted non-commercial use
> >>
> >
> > I tried to send an email to David Michael Betz
> > but the email returns. I tried to email address:
>
> There seems to be a more recent version of xlisp on this site:
> http://www.xlisp.org/
>
> It has another email address (which I've CCed). Hopefully it works!
>
> Maybe part of the solution to this bug is to update audacity's copy of
> xlisp to this new version which seems to be under the BSD 3-clause
license?
>
> (of course there are some other non-free files to look at as well)
>

The license seems to be same that is in collab-maint[0]. The
problem is some files[1] has:

|

ermission is granted for unrestricted non-commercial use

|


[0] -
https://anonscm.debian.org/cgit/pkg-multimedia/audacity.git/tree/lib-src/libnyquist/nyquist/license.txt

[1] -
https://anonscm.debian.org/cgit/pkg-multimedia/audacity.git/tree/lib-src/libnyquist/nyquist/xlisp/xlisp.c

I am a little bit confuse about SGML:

 xhtml-symbol.ent
 xhtml-special.ent
 xhtml.lat1.ent

Thera are open source alternatives, as said
here[2]:
   


Open-source implementations

Significant open-source
 implementations of
SGML have included:

  * ASP-SGML 
  * ARC-SGML ,
by Standard Generalized Markup Language Users', 1991, C language
  * SGMLS , by
James Clark, 1993, C language
  * Project YAO , by
Yuan-ze Institute of Technology, Taiwan, with Charles Goldfarb,
1994, object
  * SP  by James Clark, C++ language


[2] - https://en.wikipedia.org/wiki/SGML


Regards,
Herbert

Processed: Bug#834685 marked as pending

[Debian Bug Tracking System]

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

> tag 834685 pending
Bug #834685 [src:python-reno] python-reno: FTBFS too much often (failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#834685: marked as pending

[Thomas Goirand]

tag 834685 pending
thanks

Hello,

Bug #834685 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=openstack/python-reno.git;a=commitdiff;h=4495c4f

---
commit 4495c4fd240294f98602f0f1c40594602612b360
Author: Thomas Goirand 
Date:   Fri Sep 9 15:14:56 2016 +0200

Add gnupg as build-depends-indep (Closes: #834685).

diff --git a/debian/changelog b/debian/changelog
index 5d67118..31d9d95 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+python-reno (1.3.0-4) unstable; urgency=medium
+
+  * Add gnupg as build-depends-indep (Closes: #834685).
+
+ -- Thomas Goirand   Fri, 09 Sep 2016 14:11:39 +0200
+
 python-reno (1.3.0-3) unstable; urgency=medium
 
   * Added git as runtime and build depends (Closes: #824593).

Bug#830440: mpi4py: FTBFS: ld: cannot find -llmpe (not actual cause for build failures, test target is)

[Yaroslav Halchenko]

Thanks for looking into it Sebastiaan.

Since the beast built/tested before just fine, it is something in recent
upgrades (openmpi etc) which triggered some incompatibility issues I
guess. Before jumping into patching it, decided to check on upstream
plans regarding the release:

https://bitbucket.org/mpi4py/mpi4py/issues/50/is-new-release-210-coming

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Processed: tagging 825320

[Debian Bug Tracking System]

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

> tag 825320 + patch
Bug #825320 [src:gcc-doc-defaults] gcc-doc-defaults: FTBFS in sid: error in 
'Version' field string '5:': nothing after colon in version number
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#834180: marked as done (bristol: FTBFS: audioEngineJack.c:42:26: fatal error: alsa/iatomic.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 12:48:36 +
with message-id 
and subject line Bug#834180: fixed in bristol 0.60.11-3
has caused the Debian Bug report #834180,
regarding bristol: FTBFS: audioEngineJack.c:42:26: fatal error: alsa/iatomic.h: 
No such file or directory
to be marked as done.

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

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


-- 
834180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bristol
Version: 0.60.11-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,

bristol fails to build from source in unstable/amd64:

  [..]

  libtoolize: copying file './ltmain.sh'
  libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
  libtoolize: copying file 'm4/libtool.m4'
  libtoolize: copying file 'm4/ltoptions.m4'
  libtoolize: copying file 'm4/ltsugar.m4'
  libtoolize: copying file 'm4/ltversion.m4'
  libtoolize: copying file 'm4/lt~obsolete.m4'
  configure.ac:26: warning: AM_INIT_AUTOMAKE: two- and three-arguments forms 
are deprecated.  For more info, see:
  configure.ac:26: 
http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation
  configure.ac:31: installing './compile'
  configure.ac:26: installing './missing'
  bin/Makefile.am: installing './depcomp'
 debian/rules override_dh_auto_configure
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160812211734.6zaizKywgD.db.bristol/bristol-0.60.11'
  dh_auto_configure -- --prefix=/usr --libdir=\${prefix}/lib/bristol \
--enable-jack-default-audio --enable-jack-default-midi
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --prefix=/usr --libdir=\${prefix}/lib/bristol 
--enable-jack-default-audio --enable-jack-default-midi
  configure: WARNING: unrecognized options: --disable-maintainer-mode
  checking for a BSD-compatible install... /usr/bin/install -c
  checking whether build environment is sane... yes
  checking for a thread-safe mkdir -p... /bin/mkdir -p
  checking for gawk... no
  checking for mawk... mawk
  checking whether make sets $(MAKE)... yes
  checking whether make supports nested variables... yes
  checking build system type... x86_64-pc-linux-gnu
  checking host system type... x86_64-pc-linux-gnu
  checking how to print strings... printf
  checking for style of include used by make... GNU
  checking for gcc... gcc
  checking whether the C compiler works... yes
  checking for C compiler default output file name... a.out
  checking for suffix of executables... 
  checking whether we are cross compiling... no
  checking for suffix of object files... o
  checking whether we are using the GNU C compiler... yes
  checking whether gcc accepts -g... yes
  checking for gcc option to accept ISO C89... none needed
  checking whether gcc understands -c and -o together... yes
  checking dependency style of gcc... none
  checking for a sed that does not truncate output... /bin/sed
  checking for grep that handles long lines and -e... /bin/grep
  checking for egrep... /bin/grep -E
  checking for fgrep... /bin/grep -F
  checking for ld used by gcc... /usr/bin/ld
  checking if the linker (/usr/bin/ld) is GNU ld... yes
  checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
  checking the name lister (/usr/bin/nm -B) interface... BSD nm
  checking whether ln -s works... yes
  checking the maximum length of command line arguments... 1572864
  checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu 
format... func_convert_file_noop
  checking how to convert x86_64-pc-linux-gnu file names to toolchain format... 
func_convert_file_noop
  checking for /usr/bin/ld option to reload object files... -r
  checking for objdump... objdump
  checking how to recognize dependent libraries... pass_all
  checking for dlltool... no
  checking how to associate runtime and link libraries... printf %s\n
  checking for ar... ar
  checking for archiver @FILE support... @
  checking for strip... strip
  checking for ranlib... ranlib
  checking command to parse /usr/bin/nm -B output from gcc object... ok
  checking for 

Bug#837017: libvisio: FTBFS: Tests failures

[Rene Engelhard]

severity 837017 important
retitle 837017 libvisio: FTBFS: Tests failures with missing tzdata
tag 837017  + upstream
thanks

Hi,

n Thu, Sep 08, 2016 at 08:19:20AM +0200, Lucas Nussbaum wrote:
> Note that tzdata was missing in the chroot, but I don't see anything in
> the log that is related to time or tz, so it's likely unrelated.

importtest.cpp:71:Assertion
Test name: ImportTest::testVsdMetadataTitleUtf8
equality assertion failed
- Expected: 2014-11-26T09:24:56Z
- Actual  : 2014-11-26T08:24:56Z
- Attribute 'creation-date' of '/document/setDocumentMetaData': incorrect value
.

Failures !!!
Run: 7   Failure total: 1   Failures: 1   Errors: 0
FAIL test (exit status: 1)

sounds time-related to me :)

Indeed, when removing tzdata it fails wih the above for me.

http://pkgs.fedoraproject.org/cgit/rpms/libvisio.git/commit/?id=9a51fb2842ae0f020988d300746d16de4f4d3a01
 is also there, but then again the system probably
doesn't know CET when tzdata isn't present ;-)

Regards,

Rene

Processed: Re: Bug#837017: libvisio: FTBFS: Tests failures

[Debian Bug Tracking System]

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

> severity 837017 important
Bug #837017 [src:libvisio] libvisio: FTBFS: Tests failures
Severity set to 'important' from 'serious'
> retitle 837017 libvisio: FTBFS: Tests failures with missing tzdata
Bug #837017 [src:libvisio] libvisio: FTBFS: Tests failures
Changed Bug title to 'libvisio: FTBFS: Tests failures with missing tzdata' from 
'libvisio: FTBFS: Tests failures'.
> tag 837017  + upstream
Bug #837017 [src:libvisio] libvisio: FTBFS: Tests failures with missing tzdata
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#830440: mpi4py: FTBFS: ld: cannot find -llmpe (not actual cause for build failures, test target is)

[Sebastiaan Couwenberg]

The mpi4py build failures on the buildds are blocking multiple packages
affected by the ongoing openmpi transition.

The ld issues reported in this issue are not the actual cause of the
build failures, the test suite is killed afer 150 minutes of inactivity
on the buildds, and the full buildlog from Lucas also fails in the test
target:

 ==
 FAIL: testDL1 (test_dl.TestDL)
 --
 Traceback (most recent call last):
   File "/«PKGBUILDDIR»/test/test_dl.py", line 18, in testDL1
 self.assertTrue(handle != 0)
 AssertionError: False is not true

 --
 Ran 1007 tests in 3.864s

 FAILED (failures=1)

I cannot reproduce the build failure in my cowbuilder chroots, I can
however reproduce the timeout on the amd64 porterbox. The tests after
testScatterv3 (test_cco_nb_vec.TestCCOVecWorldDup) seem to be the
culprit, this is the last test to succeed. I've not found a fix for this
yet.

Kind Regards,

Bas

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

Bug#835966: RM: polyorb -- RoQA; unmaintained, RC-buggy

[Svante Signell]

On Thu, 2016-09-08 at 17:24 +, Mattia Rizzolo wrote:
> On Thu, Sep 08, 2016 at 07:18:08PM +0200, Svante Signell wrote:
> > 
> > I don't have a natural url place to put the changes, sorry. The
> > patches
> > were attached to my first posting in this thread and time is
> > running
> > out until the package is removed. The patches are also available in
> > bug
> > #835966.
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=835966;msg=13
> ;filename=examples_corba_echo_echo-impl.adb.patch
> https://bugs.debian.org/cgi-
> bin/bugreport.cgi?att=2;bug=835966;ms
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=835966;msg=13
> ;filename=src_csupport.c.patch
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=835966;msg=13
> ;filename=hardening.patch
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=835966;msg=13
> ;filename=debian_rules.patch
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=3;bug=835966;msg=13
> ;filename=debian_control.patch
> 
> if you want to wget them you need to quote the URLs (as due to the ;
> the
> shell would think it a series of command chained).

What's the problem? In 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835966#13
clicking on the attachments downloads/opens the patches.

Processed: block 835397 with 837152

[Debian Bug Tracking System]

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

> block 835397 with 837152
Bug #835397 [release.debian.org] transition: superlu
835397 was blocked by: 835556 835557 836677
835397 was not blocking any bugs.
Added blocking bug(s) of 835397: 837152
> thanks
Stopping processing here.

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

Bug#837090: marked as done (wordpress: CVE-2016-6896 CVE-2016-6897)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 12:19:56 +
with message-id 
and subject line Bug#837090: fixed in wordpress 4.6.1+dfsg-1
has caused the Debian Bug report #837090,
regarding wordpress: CVE-2016-6896 CVE-2016-6897
to be marked as done.

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

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


-- 
837090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wordpress
Version: 4.5.3+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi,

the following vulnerabilities were published for wordpress.

CVE-2016-6896[0] and CVE-2016-6897[1]. It was reported that they at
least affect 4.5.3, no earlier version were so far checked, since no
full details to fixes given. There are more information in [2].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-6896
[1] https://security-tracker.debian.org/tracker/CVE-2016-6897
[2] 
https://sumofpwn.nl/advisory/2016/path_traversal_vulnerability_in_wordpress_core_ajax_handlers.html
[3] http://seclists.org/oss-sec/2016/q3/341

Could you please have a look at those, and please adjust the affected
versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 4.6.1+dfsg-1

We believe that the bug you reported is fixed in the latest version of
wordpress, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Sep 2016 21:56:22 +1000
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentysixteen 
wordpress-theme-twentyfifteen wordpress-theme-twentyfourteen
Architecture: source all
Version: 4.6.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files
 wordpress-theme-twentyfourteen - weblog manager - twentyfourteen theme files
 wordpress-theme-twentysixteen - weblog manager - twentysixteen theme files
Closes: 837090
Changes:
 wordpress (4.6.1+dfsg-1) unstable; urgency=medium
 .
   * New upstream security release, Closes: #837090, fixes CVE-2016-6896 and
 CVE-2016-6897
Checksums-Sha1:
 1d4358c33837111fffc3128aca33c33f393e52be 2523 wordpress_4.6.1+dfsg-1.dsc
 3cc461c5d25a15e7e7b9552cf852fea30c656ab1 6154728 
wordpress_4.6.1+dfsg.orig.tar.xz
 7523306d85a2eac628343a9ebc4aca1b627d986a 6950416 
wordpress_4.6.1+dfsg-1.debian.tar.xz
 3dea5f97150d628b550da45aedd0c64165c4771d 4239702 
wordpress-l10n_4.6.1+dfsg-1_all.deb
 fc874711e5a97944b7ae6bdfee0fdb6cf26a66a4 698828 
wordpress-theme-twentyfifteen_4.6.1+dfsg-1_all.deb
 4890067b6ad0b8cb52ad0e1be3e1d23995560845 1120184 
wordpress-theme-twentyfourteen_4.6.1+dfsg-1_all.deb
 a3b54e972bf5ccc1804dc2bcbd650344b14906a9 587770 
wordpress-theme-twentysixteen_4.6.1+dfsg-1_all.deb
 aef631a3f0d255d25cfa8ee5958bed64c929d019 3830938 wordpress_4.6.1+dfsg-1_all.deb
Checksums-Sha256:
 8afbb07db08474fc309cec9c825705bd8cf9dd30c62d88082e41552c6358 2523 
wordpress_4.6.1+dfsg-1.dsc
 1ddf59a393d5bfad357790c1e2a8cc18e2d39724f91135606517ed4f2d8c35b1 6154728 
wordpress_4.6.1+dfsg.orig.tar.xz
 1bcd6fbb3cba02616f67881499f8dbd9aa271e7493074d5a953bfc795e7b3d29 6950416 
wordpress_4.6.1+dfsg-1.debian.tar.xz
 61a52bcba80b3439734a4da8a1bb07a29e4429be37aeb965cd53375fdb61a2d1 4239702 
wordpress-l10n_4.6.1+dfsg-1_all.deb
 0931b4c96bbb24c9896c21957f5e35d79e1b80e396721d071fcf956cc8789ea6 698828 
wordpress-theme-twentyfifteen_4.6.1+dfsg-1_all.deb
 7a93f7d8a6c9d885c54baf00b840a3e493301b158f50a61d77fc7b9705ea3328 1120184 
wordpress-theme-twentyfourteen_4.6.1+dfsg-1_all.deb
 

Bug#837136: marked as done (libgtk3-perl: FTBFS: t/overrides.t failure)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 11:49:40 +
with message-id 
and subject line Bug#837136: fixed in libgtk3-perl 0.028-2
has caused the Debian Bug report #837136,
regarding libgtk3-perl: FTBFS: t/overrides.t failure
to be marked as done.

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

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


-- 
837136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk3-perl
Version: 0.028-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

As noticed by ci.debian.net at
 http://ci.debian.net/packages/libg/libgtk3-perl/unstable/amd64/

this package fails its test suite on current sid, making it fail to
build from source.

  (overrides.t:10670): Gtk-WARNING **: Theme parsing error: :1:30: Using 
Pango syntax for the font: style pro
  perty is deprecated; please use CSS syntax
  :1:17not a number at /<>/blib/lib/Gtk3.pm line 968.
  # Looks like you planned 215 tests but ran 25.
  # Looks like your test exited with 25 just after 25.

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libgtk3-perl
Source-Version: 0.028-2

We believe that the bug you reported is fixed in the latest version of
libgtk3-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libgtk3-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Sep 2016 13:41:22 +0200
Source: libgtk3-perl
Binary: libgtk3-perl
Architecture: source
Version: 0.028-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 837136
Description: 
 libgtk3-perl - Perl bindings for the GTK+ graphical user interface library
Changes:
 libgtk3-perl (0.028-2) unstable; urgency=medium
 .
   * Team upload.
   * Add a patch from CPAN RT to fix a test failure caused by a warning
 about Pango markup in newer gtk3. (Closes: #837136)
   * Add a patch to fix a typo in the documentation.
   * debian/*: use HTTPS for two URLs.
   * debian/control: drop explicit build dependency on Test::More.
 Already satisfied in oldstable.
Checksums-Sha1: 
 7edfdc4e97a6e6b264466b7df8ffb89aaf56e93a 2288 libgtk3-perl_0.028-2.dsc
 3e87ad0522e5414560b6900ba2e9a0d52e18d087 5268 
libgtk3-perl_0.028-2.debian.tar.xz
Checksums-Sha256: 
 851c62e2fdf73a47de7115576875a5001c3e1ec38b607454906e8eadfc440b11 2288 
libgtk3-perl_0.028-2.dsc
 8f57f7895cf2a24e18b61768a9b70c9763dccddb4028e8a0cc13647f33d33ac1 5268 
libgtk3-perl_0.028-2.debian.tar.xz
Files: 
 0a431e37fc4e46f31c319c5430c6f030 2288 perl optional libgtk3-perl_0.028-2.dsc
 90f0576dc24aff275a49b847ca726ae1 5268 perl optional 
libgtk3-perl_0.028-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJX0qBqXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGzoQP/iLn9l8ZYts7EVQXztrAznug
cfK5yV8m9V1BJBUcBzRle+v4WwPMIvqlecrTjsnUzEVleFUEX7oDB67/3iVp+nyP
AVsDJPk/Q1eVGJ7pVIMejz66F2lHrYRMoXEpE0X0NlNFKihISlnOm0lej9GEHf/M
gtAojGmskL0pQ7T1bzCsBNGJzd/BiHMyCE9bs7deMYpGWwEbsIQ7L7iSwMswuTS4
oDirxrFnvedGUdv710CjEGa2+W13gqcXVfyEg7GgdP+qMrMhNBHe7wAADvDrBqYe
8icEAlTNzEhYuUxTert/Gl9C+2ZqI4m33xdah6y+5yIeJvRt98IVGcPUYq4sHW7I
lfX8952FMhLsVkoEq9Z+orj4yLIh48p89XNn+/zEiVNLatw5SKEUy8TdTfeLQp7L
d88Ig1W0sVt7JDt510AnSXHmRgAbu2X3ZVxksT8nxHN9K9tG5p9a+jVUfcJzNl9D
UU/8ZiwzFH2aCfZgg6czNZptL4GUwac2/3N6AR5hKWqD46RWU5i0Qtmu8Jud42XI
36t+iEZBu/+7MAnCss3GY7IqSpjYAa6UzRL1wHVH7PTFDZ9aKSmAAo8KaffJsnFi
5BCUrDDZyONtkjsz4hlSccIO9DNnPR3L7StX4lNnEE+gEk3dJADPNfpihRG7I+Tj
utu3P2/LTJ0kXbkdBHZy
=7MLz
-END PGP SIGNATURE End Message ---

Bug#837136: Pending fixes for bugs in the libgtk3-perl package

[pkg-perl-maintainers]

tag 837136 + pending
thanks

Some bugs in the libgtk3-perl package are closed in revision
51b9bf066f88e9513de044df6427706cbddca677 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libgtk3-perl.git/commit/?id=51b9bf0

Commit message:

Add a patch from CPAN RT to fix a test failure

caused by a warning about Pango markup in newer gtk3.

Closes: #837136

Processed: Pending fixes for bugs in the libgtk3-perl package

[Debian Bug Tracking System]

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

> tag 837136 + pending
Bug #837136 [libgtk3-perl] libgtk3-perl: FTBFS: t/overrides.t failure
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#835708: [NMU] Re: Bug#835708: plplot: FTBFS: Tests failures

[Axel Beckert]

Control: retitle -1 plplot: FTBFS: cairo-related files are no more built
Control: tag -1 - pending

Hi again,

Axel Beckert wrote:
> > dh_movefiles --package=libplplot-ocaml
> > dh_movefiles: debian/tmp/usr/lib/ocaml/plcairo/META not found (supposed to 
> > put it in libplplot-ocaml)
> > debian/rules:147: recipe for target 'install-arch' failed
> > make: *** [install-arch] Error 1
> > dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit 
> > status 2
> > 
> > So it seems as if the issue is somewhere in the ocaml bindings.
> 
> It seems as if the files for /usr/lib/ocaml/plcairo/ are no more built
> for a reason unknown to me and independent of plplot. The remaining
> libraries to be put into the libplplot-ocaml are still build.
> 
> Since /usr/lib/ocaml/plcairo/ seems to be only one part of the
> libplplot-ocaml package and the remaining part looks functioning
> without it, I decided to sacrifice that half of libplplot-ocaml to fix
> the FTBFS and hence save all reverse dependencies from being removed
> from testing. (libplplot-ocaml seems to have no reverse dependencies
> not built from the plplot source package.)

Unfortunately this had another side-effect which I didn't notice (or
to be more precise: which I partially noticed but didn't relate to my
own changes):

FTP Masters wrote:
| plplot12-driver-cairo: lintian output: 
'usr-share-doc-symlink-without-dependency libplplot12', automatically rejected 
package.
| plplot12-driver-cairo: lintian output: 'empty-binary-package ', automatically 
rejected package.

Only the first one was considered an error by Lintian and was noticed
by me, but I somehow expected that this must have been the case before
as I didn't change something on this package.

But the probably the same cause that let /usr/lib/ocaml/plcairo/ no
more be build for libplplot-ocaml also made the contents of
plplot12-driver-cairo and hence also the (automatic) dependency of
plplot12-driver-cairo to libplplot12 vanish -- which I didn't notice.
Maybe next time I should diff the lintian output to see which warnings
are new -- plplot currently throw 87 lintian warnings, so I didn't
notice the few additional ones caused by my changes.

> After this mail, I'll upload an according fix as NMU to DELAYED/2.
> Full source debdiff and libplplot-ocaml binary debdiff following. Feel
> free to tell me to fast-forward or delay the upload a little bit more.

So the question is how to continue:

One option is obviously to not only drop /usr/lib/ocaml/plcairo/ from
libplplot-ocaml, but also the whole plplot12-driver-cairo package. But
I've dropped already enough from this package with NMUs to fix FTBFS.

Since plplot12-driver-cairo doesn't seem have any Ocaml relation, I
guess that looking for the FTBFS in the Ocaml world was a red herring.

I probably should rather focus on recent cairo-related changes
instead. But then again, there was no cairo upload at all in the short
time fram between my previous NMU (8th of August) and the report of
FTBFS (28th of August): https://packages.qa.debian.org/p/plplot.html

Using the brand new, not yet released which-pkg-broke-build[1] tool
from the debian-goodies package, these (recursive) build-dependencies
changed in that time frame:

(The list misses Tcl/Tk stuff since I prefer 8.6 over 8.5. BTW: It
seems as if newer upstream versions of plplot build fine again with
Tcl/Tk 8.6. Yes, I tried that, too, to see if it solves this issue.)

openjdk-8-jre-headless:amd64  08/08/16  02:07:10
libxml-libxml-perl08/09/16  01:06:59
libnet-ssleay-perl08/09/16  12:01:14
libpcsclite1:amd6408/11/16  00:49:08
libxcb1-dev:amd64 08/11/16  09:13:28
libxcb1:amd64 08/11/16  09:13:28
libxcb-shm0:amd64 08/11/16  09:13:30
libxcb-render0:amd64  08/11/16  09:13:31
ghostscript   08/11/16  19:46:25
libgs908/11/16  19:46:26
libgs9-common 08/11/16  19:46:27
libtasn1-6:amd64  08/13/16  22:55:15
libarchive-zip-perl   08/13/16  22:55:17
libsqlite3-0:amd6408/14/16  19:54:00
debhelper 08/14/16  19:54:02
libaudit-common   08/15/16  18:36:57
libaudit1:amd64   08/15/16  18:37:01
bsdutils  08/16/16  00:26:00
util-linux08/16/16  00:26:05
libuuid1:amd6408/16/16  00:26:16
libblkid1:amd64   08/16/16  00:26:20
libfdisk1:amd64   08/16/16  00:26:24
libmount1:amd64   08/16/16  00:26:28
libsmartcols1:amd64   08/16/16  00:26:32
libdbus-1-3:amd64 08/16/16  12:02:49
libnspr4:amd6408/16/16  12:02:52
libnss3:amd64 08/16/16  20:59:24
dblatex   08/16/16  20:59:40
fonts-dejavu-core 08/17/16  01:05:38

Processed: Re: Bug#835708: [NMU] Re: Bug#835708: plplot: FTBFS: Tests failures

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 plplot: FTBFS: cairo-related files are no more built
Bug #835708 [src:plplot] plplot: FTBFS: Tests failures
Changed Bug title to 'plplot: FTBFS: cairo-related files are no more built' 
from 'plplot: FTBFS: Tests failures'.
> tag -1 - pending
Bug #835708 [src:plplot] plplot: FTBFS: cairo-related files are no more built
Removed tag(s) pending.

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

Processed: bug 837136 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=114162, tagging 837136

[Debian Bug Tracking System]

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

> forwarded 837136 https://rt.cpan.org/Public/Bug/Display.html?id=114162
Bug #837136 [libgtk3-perl] libgtk3-perl: FTBFS: t/overrides.t failure
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=114162'.
> tags 837136 + confirmed upstream patch
Bug #837136 [libgtk3-perl] libgtk3-perl: FTBFS: t/overrides.t failure
Added tag(s) patch, confirmed, and upstream.
> thanks
Stopping processing here.

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

Bug#837086: marked as done (tea: FTBFS on the arch:all buildd (dpkg-buildpackage -A))

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 10:27:42 +
with message-id 
and subject line Bug#837086: fixed in tea 42.0.0-3
has caused the Debian Bug report #837086,
regarding tea: FTBFS on the arch:all buildd (dpkg-buildpackage -A)
to be marked as done.

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

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


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

Hi,

tea FTBFS while building only arch-indep packages (as with
dpkg-buildpackage -A, such as done on the arch:all buildds):

https://buildd.debian.org/status/fetch.php?pkg=tea=all=42.0.0-2=1473268741

   debian/rules override_dh_install
make[1]: Entering directory '/«PKGBUILDDIR»'
dh_install
cp icons/tea-icon-v3-02.png 
/«PKGBUILDDIR»/debian/tea/usr/share/icons/hicolor/128x128/apps/tea.png
cp: cannot create regular file 
'/«PKGBUILDDIR»/debian/tea/usr/share/icons/hicolor/128x128/apps/tea.png': No 
such file or directory
debian/rules:17: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1


Andreas
--- End Message ---
--- Begin Message ---
Source: tea
Source-Version: 42.0.0-3

We believe that the bug you reported is fixed in the latest version of
tea, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 837...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated tea package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 09 Sep 2016 11:34:53 +0200
Source: tea
Binary: tea tea-data
Architecture: source
Version: 42.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Dr. Tobias Quathamer 
Changed-By: Dr. Tobias Quathamer 
Description:
 tea- graphical text editor with syntax highlighting
 tea-data   - graphical text editor with syntax highlighting - data files
Closes: 837086
Changes:
 tea (42.0.0-3) unstable; urgency=medium
 .
   * Fix FTBFS: Use original name for icon.
 Thanks to Andreas Beckmann  (Closes: #837086)
Checksums-Sha1:
 02487b0c81118c62e7edd125f883a5ef3ff82527 1968 tea_42.0.0-3.dsc
 873f171939d961f791e2d7f52a4d84bb93a0663b 7188 tea_42.0.0-3.debian.tar.xz
Checksums-Sha256:
 8225466777a6258bea94861e1d9f83cd70020d75a944712b5a224d9354789b51 1968 
tea_42.0.0-3.dsc
 8ed42ac15ff2daf76f69d01169415861c894aa5c0547fca3151728a479a4bfa9 7188 
tea_42.0.0-3.debian.tar.xz
Files:
 5dd209e355b46b1d1b1beb9ffb912426 1968 editors optional tea_42.0.0-3.dsc
 f6a25ff8db4a7a55bc2069a1f0966c5d 7188 editors optional 
tea_42.0.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX0oVbAAoJEBMC8fA26+sZ4QcP/iaZ6RNPKuRaPkyN8yq2clc4
f4Pe6p89STCsNYub4IsZD8V784bVdOULEMQ03S3Y/xe4sBuTaNUUvfwtPE9C2SZj
FeT/XhE5+0T+tJrWoY8bsUGVyqK/B0n48QbG3HuRQOiJ33BZ7Ic8kWfu24aWGzAH
VKFDiOffDkOXlhETL5VnUaNYSN1yQF7WAPMg0V0aph3vXvSRSR9fWWgBE5FgfgHJ
RuFrtk/J5nr8B3Wm+hRUnkyxPi5aGQuUGckfizh0rq3Nb6sQYdjCPXQ49+3krNn3
hdAA7nntVfE2J7vROsb8IHoMzL6BFdEha7ROQvRuXVWsRX6/BtZF2trjASoiphAT
UuqTqUed9SPsfhcTOPHbwjeasqMzXA/K3n+xVPZBxk9ePm6TmVbh+QukM3HB7sFS
x7ST9IkY4qNB/+1tsde3bCM3wMKAgDwV8XfeaJh/6Kk1glhnJ5HgxxyoN+OWkjmq
wIjl0cheA6VBZuwDmxqkZYNCdlQmmv5yW1IpYDRF/Z/cJDAgxOPeynJgXKopjSaQ
V/HET19rXMTQqRB33mQnVgVfQ8NWAO5nNAFoG5jg2sB1uP3I42TBmqZIZWERjz/9
G8mJ/YcIsjTq8EW3pJ43af4wgGoXKGuUJ3a9cXeR7xO2o+ZyzE/DVrjO+LhgAhMb
CwLyripe9F+qzi4BNKQ7
=NthF
-END PGP SIGNATURE End Message ---

Bug#836732: marked as done (strip-nd: FTBFS when locale is not English)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 10:27:25 +
with message-id 
and subject line Bug#836732: fixed in strip-nondeterminism 0.026-1
has caused the Debian Bug report #836732,
regarding strip-nd: FTBFS when locale is not English
to be marked as done.

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

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


-- 
836732: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: strip-nondeterminism
version: 0.024-1
severity: serious

As you can see in reproducible-builds buildlogs, strip-nd fails to build
when locale is not English, i.e. in the second build.

For example, for Italian:

| All tests successful.
| Files=2, Tests=15, 59 wallclock secs ( 0.33 usr  0.03 sys + 55.59 cusr  2.80 
csys = 58.75 CPU)
| Result: PASS
| sh: riga 0: return: è possibile eseguire "return" solo da una funzione o da 
uno script chiamato
| sh: riga 0: test: OPTIMIZE=-O0 -fprofile-arcs -ftest-coverage: atteso 
operatore unario
| Reading database from /build-2nd/strip-nondeterminism-0.025/cover_db
| 
| 
| --- -- -- -- -- -- --
| File  stmt   bran   condsub   time  total
| --- -- -- -- -- -- --
| .../lib/File/StripNondeterminism.pm   78.5   40.0   66.6   92.8   97.1   67.5
| ...le/StripNondeterminism/Common.pm  100.0n/an/a  100.00.0  100.0
| ...ripNondeterminism/handlers/ar.pm  100.0   64.2   50.0  100.00.0   89.0
| ...ndeterminism/handlers/gettext.pm   20.60.00.0   66.60.6   18.1
| ...pNondeterminism/handlers/gzip.pm   79.6   42.5   33.3  100.00.0   65.8
| ...ipNondeterminism/handlers/jar.pm   62.0   23.0   33.3   84.61.7   53.4
| ...ndeterminism/handlers/javadoc.pm   95.8   63.6   33.3  100.00.0   83.3
| ...inism/handlers/javaproperties.pm   97.2   62.5   33.3  100.00.0   86.2
| ...rminism/handlers/pearregistry.pm  100.0   50.0   40.0  100.00.0   86.2
| ...ipNondeterminism/handlers/png.pm   97.3   73.3  100.0  100.00.1   91.7
| ...ipNondeterminism/handlers/zip.pm   79.7   38.4   41.6   85.70.0   69.8
| Total 79.3   43.6   50.0   92.7  100.0   69.8
| --- -- -- -- -- -- --
| 
| 
| HTML output written to 
/build-2nd/strip-nondeterminism-0.025/cover_db/coverage.html
| done.
| debian/rules:10: set di istruzioni per l'obiettivo "override_dh_auto_test" 
non riuscito
| make[1]: *** [override_dh_auto_test] Errore 2
| make[1]: uscita dalla directory "/build-2nd/strip-nondeterminism-0.025"
| debian/rules:13: set di istruzioni per l'obiettivo "build" non riuscito
| make: *** [build] Errore 2
| dpkg-buildpackage: error: debian/rules build gave error exit status 2
| I: copying local configuration
| E: Failed autobuilding of package


The sh errors above translates to
sh: line 0: return: is possible to execute "return" only from a function or 
from a script called
sh: line 0: test: OPTIMIZE=-O0 -fprive-arcs -ftest-coverage: exepected 
unary operator

Not sure how much related they are, but I guess it means something given
that it's not in the English build.


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: strip-nondeterminism
Source-Version: 0.026-1

We believe that the bug you reported is fixed in the latest version of
strip-nondeterminism, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated strip-nondeterminism package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Sep 2016 11:02:04 +0100
Source: 

Bug#835247: marked as done (FTBFS against pytest 3.0.0)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 10:26:04 +
with message-id 
and subject line Bug#835247: fixed in python-wrapt 1.9.0-1
has caused the Debian Bug report #835247,
regarding FTBFS against pytest 3.0.0
to be marked as done.

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

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


-- 
835247: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-wrapt
Version: 1.8.0-5
Severity: important
Tags: sid stretch
Usertags: pytest3.0.0

python-wrapt runs py.test-X.Y during the build. This entry point was dropped
in pytest 3.0.0. Please use `pythonX.Y -m pytest` instead.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-wrapt
Source-Version: 1.9.0-1

We believe that the bug you reported is fixed in the latest version of
python-wrapt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 835...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-wrapt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Sep 2016 08:05:11 +
Source: python-wrapt
Binary: python-wrapt python3-wrapt python-wrapt-doc
Architecture: source amd64 all
Version: 1.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Thomas Goirand 
Description:
 python-wrapt - decorators, wrappers and monkey patching. - Python 2.x
 python-wrapt-doc - decorators, wrappers and monkey patching. - doc
 python3-wrapt - decorators, wrappers and monkey patching. - Python 3.x
Closes: 765064 835247
Changes:
 python-wrapt (1.9.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URLs (https).
   * d/rules: Changed UPSTREAM_GIT protocol to https
 .
   [ Thomas Goirand ]
   * New upstream release (Closes: #765064):
 - Drop do-not-use-embedded-six.py.patch and
   no-from-wrapt-import-six-in-tests.patch, as src/six.py is gone upstream.
 - Drop fix-python-3.4-compat.patch applied upstream.
 - Drop python-3.2-compat.patch as upstream isn't using embedded six.
   * Standards-Version is now 3.9.6 (no change).
   * Removed non-active maintainers.
   * Reviewed (build-)depends and ran wrap-and-sort -t -a.
   * Simplified debian/rules using goodies from openstack-pkg-tools >= 52~.
   * Using python$$pyvers -m pytest to run tests (Closes: #835247).
   * Fixed debian/copyright ordering.
   * Standards-Version: 3.9.8 (no change).
   * Added export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow.
   * Removed do-not-use-the-rdt-sphinx-theme.patch and build-depends on the
 python-sphinx-rtd-theme package.
Checksums-Sha1:
 43b76fd5538c44db8a108683ab3557b99c700584 2313 python-wrapt_1.9.0-1.dsc
 2e7db5e15902b4bc3a463d6d09d038e5f6e1d933 80648 python-wrapt_1.9.0.orig.tar.xz
 fa605f6e623e4a44a84d746fa0105464f496de4a 4980 
python-wrapt_1.9.0-1.debian.tar.xz
 85b991d222ccc23c194b8db2559456a7591daad4 29044 
python-wrapt-dbgsym_1.9.0-1_amd64.deb
 2429a6eb9297126513fddcda0c30f1d6eac3703d 55814 python-wrapt-doc_1.9.0-1_all.deb
 c18e5082b631503e91898a10f9c4b5a520532e92 31358 python-wrapt_1.9.0-1_amd64.deb
 a3c3f6dd9a2004bc64424e4d739c02f9ae3386a0 31528 
python3-wrapt-dbgsym_1.9.0-1_amd64.deb
 5b8b0b1d8d3c014d88aa1efcf7c72b382fda1bd7 31338 python3-wrapt_1.9.0-1_amd64.deb
Checksums-Sha256:
 0e789528cf1a5a09718f21241d3db131174ab29df21b87253de57103914b7ca7 2313 
python-wrapt_1.9.0-1.dsc
 2a07d6cf4e192bb18c4c980ddc746dfceb7ada3a80979127c48fe7c604343c19 80648 
python-wrapt_1.9.0.orig.tar.xz
 ac5913fefa8f07d0f5c98d76d03573e00b5affa3040b242e738b285823e47963 4980 
python-wrapt_1.9.0-1.debian.tar.xz
 a0433ca5691773c6683bf284027c7eeadc34d394a214a40ccc628bad7ab2b5e5 29044 
python-wrapt-dbgsym_1.9.0-1_amd64.deb
 571d2f962c13879ca393097f957c6a2eabc91f376d66e8ab6a0f489efad61086 55814 
python-wrapt-doc_1.9.0-1_all.deb
 52a46ed79c0b389bb4e7ba4780c0e3ec3219cb52c596fd5c145bbae9d4cd0006 31358 
python-wrapt_1.9.0-1_amd64.deb
 

Bug#836778: marked as done (btrfs-progs 4.7 and 4.7.1 report numerous, various, incorrect backref problems)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 10:19:47 +
with message-id 
and subject line Bug#836778: fixed in btrfs-progs 4.7.2-1
has caused the Debian Bug report #836778,
regarding btrfs-progs 4.7 and 4.7.1 report numerous, various, incorrect backref 
problems
to be marked as done.

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

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


-- 
836778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: btrfs-progs
Version: 4.7-1
Control: tags -1 upstream

https://bugzilla.kernel.org/show_bug.cgi?id=155791
http://www.spinics.net/lists/linux-btrfs/msg58142.html

David Sterba says a fix is on the way and planned for 4.7.2 :-)  <
https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg57085.html
>

Cheers,
Nicholas
--- End Message ---
--- Begin Message ---
Source: btrfs-progs
Source-Version: 4.7.2-1

We believe that the bug you reported is fixed in the latest version of
btrfs-progs, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated btrfs-progs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 08 Sep 2016 12:27:38 +0100
Source: btrfs-progs
Binary: btrfs-progs btrfs-tools btrfs-progs-udeb btrfs-progs-dbg btrfs-tools-dbg
Architecture: source
Version: 4.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Dimitri John Ledkov 
Changed-By: Dimitri John Ledkov 
Description:
 btrfs-progs - Checksumming Copy on Write Filesystem utilities
 btrfs-progs-dbg - Checksumming Copy on Write Filesystem utilities (debug)
 btrfs-progs-udeb - Checksumming Copy on Write Filesystem utilities (udeb) 
(udeb)
 btrfs-tools - transitional dummy package
 btrfs-tools-dbg - transitional dummy package
Closes: 836778
Changes:
 btrfs-progs (4.7.2-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #836778)
Checksums-Sha1:
 e81be12f2fd0b389553926ac5d7a2268867f93c8 1934 btrfs-progs_4.7.2-1.dsc
 7c589fc44438b1961a996e1e4cb1ec9ea2f1af2a 1320812 btrfs-progs_4.7.2.orig.tar.xz
 f6378556514d6ed5202c9611f2bd1c63fda016dd 13632 
btrfs-progs_4.7.2-1.debian.tar.xz
Checksums-Sha256:
 46d6fec202e57411303a0e1411349597a67cbe10acb4642971dfa9a419d7d620 1934 
btrfs-progs_4.7.2-1.dsc
 f49bc9e143ffe60260c5bd70ef3b624576673f8b50f41e309892a425f7fbe60f 1320812 
btrfs-progs_4.7.2.orig.tar.xz
 bcbdbd4eec25dd9fe389dd1cca4339ec7040edc1652834e35e6c029a7f947baf 13632 
btrfs-progs_4.7.2-1.debian.tar.xz
Files:
 91c8e85aa7f7a1632c64818fd7f0b9de 1934 admin optional btrfs-progs_4.7.2-1.dsc
 0cc94ee801027ea06c357bbb9906b987 1320812 admin optional 
btrfs-progs_4.7.2.orig.tar.xz
 8f82bb7d3d23d2bb67e5d5d7a2ece82f 13632 admin optional 
btrfs-progs_4.7.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJX0UzHAAoJEMrC2LnNLKX53wIIAI1+RXtwykhDksFNphJ3AjWx
MngBUfgz83Xq1JpEsmOcTOq4tw6TCckrGGuT+WkdA03fmbMwiCB6KNkOYtCateC5
sWqTee7OIyGAzOwRsWakRBMHnt5RCpseCooepGrTxnkaYbliNn/ra3MvsaIh/cYX
K/Ty9u3PPd7kDoEatpYU5AR3pRrEUQGJG7Yyrpzevhgg3WsbSMaBCyZ1yDAO4bnM
lWc/vkSn7mOSPFb3gC7oe9PszovOhWzX8AZg55t2etdQUkHQp1a+s5lPH//f0BgJ
NZwUIpesYSwGIFmJMc9BCb1jW0OtK8vaqTRxYwuhkT0cTeJnBXiMIiziLzUj3O4=
=j1lY
-END PGP SIGNATURE End Message ---

Bug#834964: testresources: FTBFS too much often (failing tests)

[Santiago Vila]

On Fri, 9 Sep 2016, Thomas Goirand wrote:

> With an up-to-date Sid, I couldn't reproduce this issue. Therefore, I'm
> closing this bug. Feel free to continue discussing it even when it has
> the closed status if you want to continue investigating.

The bug said stretch, and you tried sid, so you didn't really try to
reproduce it. Only because of this, you have already closed the bug
improperly, as you claim unreproducibility without actually testing it
the way it was reported.

If someone reports that "ls -l" segfaults, we don't close the bug
claiming "unreproducibility" after checking that "ls" alone or
"ls --color" does not segfault.

Also, the bug said "FTBFS too much often". If you only tried to build
it once, you didn't try to reproduce it either, as you can't conclude
that the probability of something is zero just by trying it once.

The evidence I showed was my own build log and the build log from
reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/testing/amd64/testresources.html

which also happened in testing at the time I reported this.

My autobuilder and the one from reproducible builds are completely
independent and not related at all, so this may not be a happy coincidence.

We do even use different build systems, they use pbuilder, I use sbuild.

Moreover, the error messages are exactly the same:


FAIL:
testresources.tests.test_optimising_test_suite.TestGraphStuff.testBasicSortTests
--
testtools.testresult.real._StringException: Traceback (most recent
call last):
  File
"/build/testresources-1.0.0/testresources/tests/test_optimising_test_suite.py",
line 527, in testBasicSortTests
"failed with permutation %s" % (permutation,))
  File "/usr/lib/python3/dist-packages/testtools/testcase.py",
line 356, in assertIn
self.assertThat(haystack, Contains(needle), message)
  File "/usr/lib/python3/dist-packages/testtools/testcase.py",
line 435, in assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: [test_three, test_one,
test_two, test_four] not in [[test_one, test_two, test_three,
test_four], [test_three, test_two, test_one, test_four]]: failed with
permutation [test_one, test_two, test_three, test_four]


And you claim that there is probably not a bug anywhere by closing the
report, despite evidence enough that there is a bug indeed?

I'm attaching three more build logs. Would you reopen the bug now, or
would you prefer that I ask the Release Managers to reopen it for you?

Thanks.

testresources_1.0.0-1_amd64-20160909T091418Z.gz
Description: application/gzip


testresources_1.0.0-1_amd64-20160909T091540Z.gz
Description: application/gzip


testresources_1.0.0-1_amd64-20160909T091554Z.gz
Description: application/gzip

Bug#837123: [anna] segfault in wheezy installer

[Aurelien Jarno]

Hi,

On 2016-09-09 10:27, Vincent McIntyre wrote:
> 
> Package: libc6-udeb
> Version: 2.13-38+deb7u10
> Severity: grave
> Justification: breaks installation entirely
> 
> The wheezy installer fails with anna reporting a segfault:
>
> ...
> anna[5033]: DEBUG: retrieving libc6-udeb 2.13-38+deb7u10
> anna[5033]: DEBUG: retrieving finish-install 2.41wheezy1
> anna[5033]: DEBUG: Segmentation fault
> anna[5033]: WARNING **: package retrieval failed
> kernel: [   66.427372] wget[5382]: segfault a 0 ip 7176c922c0ca sp 
> 7ffc8ca83890 error 6 in libresolv-2.13.so[7f76c9222000+13000]
> 
> This occurs shortly after libc6-udev is downloaded,
> according to the installer interactive display.

Unfortunately I am not able to reproduce the issue here. Given it
involves name resolving, I wouldn't be surprised it depends on the DNS
servers being used.


> Background
> --
> I was trying to reinstall an older system with wheezy.
> I was using the PXE install image available on 2016-09-08 UTC, at
> ftp.au.debian.org/debian/dists/wheezy/main/installer-amd64/current/images/netboot
> 
> The mirror shows the last update timestamp as 2016-05-31.
> debian-installer/amd64/boot-screens/f1.txt has the fairly useless
> build date stamp 20130613+deb7u3+b2.
> 
> This installation method was working fine with earlier installer
> versions. The breakage has been there some months I'd say.
> I only became fully aware of it yesterday.
> 
> I don't think the mirror is out of date; I got the same result
> with the netboot installer image downloaded from ftp.us.debian.org.
> 
> 
> The log above was copied by eye from the console,
> I was unable to install the openssh-client=udeb to copy the logs,
> thanks to the segfault.
> 
> The core of the issue is probably screwed up libc6 versions,
> see bugs 740068, 833432

It indeeds looks like that, that said the build logs actually show that
debian-installer 20130613+deb7u3+b2 has been built against glibc
2.13-38+deb7u10, so there is no version skew in this case.

Unfortunately, without being able to reproduce the problem, it will be
very difficult to debug it.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Tagging #806005

[Debian Bug Tracking System]

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

> tags 806005 + pending
Bug #806005 [src:charmap.app] charmap.app: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#837153: pdns-recursor fails to start because of missing protobuf library

[Sérgio Carvalho]

Package: pdns-recursor
Version: 4.0.2-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

pdns-recursor in recently updated debian sid installations fails to
start with the error:

/usr/sbin/pdns_recursor: symbol lookup error: /usr/sbin/pdns_recursor:
undefined symbol: _ZN6google8protobuf15UnknownFieldSet9AddVarintEim

I believe the package is linked to a no longer existing libprotobuf.

   * What led up to the situation?

A regular dist-upgrade of debian sid.

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

No action possible, other than recompiling the package.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (300, 'testing'), (100, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-1-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 pdns-recursor depends on:
ii  adduser3.115
ii  dns-root-data  2015052300+h+1
ii  init-system-helpers1.42
ii  libatomic1 6.2.0-3
ii  libboost-system1.61.0  1.61.0+dfsg-2.1
ii  libboost-thread1.61.0  1.61.0+dfsg-2.1
ii  libc6  2.24-2
ii  libgcc11:6.2.0-3
ii  liblua5.2-05.2.4-1.1
ii  libprotobuf10  3.0.0-7
ii  libssl1.0.21.0.2h-1
ii  libstdc++6 6.2.0-3
ii  libsystemd0231-5
ii  lsb-base   9.20160629

pdns-recursor recommends no packages.

pdns-recursor suggests no packages.

-- Configuration Files:
/etc/powerdns/recursor.conf changed:
export-etc-hosts=on
local-address=127.0.0.1,192.168.100.1
local-port=53
query-local-address6=
quiet=yes
setgid=pdns
setuid=pdns


-- debconf-show failed


-- 
Sérgio Carvalho

Processed: armadillo: Dependencies not satisfiable (superlu updated to 5.2.1)

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:qgis src:gdal src:pktools src:vtk6
Bug #837152 [src:armadillo] armadillo: Dependencies not satisfiable (superlu 
updated to 5.2.1)
Added indication that 837152 affects src:qgis, src:gdal, src:pktools, and 
src:vtk6

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

Bug#837152: armadillo: Dependencies not satisfiable (superlu updated to 5.2.1)

[Bas Couwenberg]

Source: armadillo
Version: 1:6.700.6+dfsg-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:qgis src:gdal src:pktools src:vtk6

Dear Maintainer,

superlu has been updated to version 5.2.1 in unstable, which makes
the armadillo packages uninstallable due to the version 4.3 constraint.

This affects all reverse dependencies of armadillo.

Version 1:7.400.1+dfsg-1 in experimental does not have the superlu 4.3
version constraint, but will require a transition. Please coordinate the
armadillo transition with the Release Team as soon as possible, or fix
the superlu dependency issue for the version in unstable in the mean
time.

Kind Regards,

Bas

Bug#834964: marked as done (testresources: FTBFS too much often (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 9 Sep 2016 10:40:46 +0200
with message-id <6fc22e13-5c5a-6ce6-cf61-4c1de3893...@debian.org>
and subject line Cannot reproduce
has caused the Debian Bug report #834964,
regarding testresources: FTBFS too much often (failing tests)
to be marked as done.

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

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


-- 
834964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834964
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:testresources
Version: 1.0.0-1
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
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
dh build-indep --buildsystem=python_distutils --with python2,python3
   dh_testdir -i -O--buildsystem=python_distutils
   dh_update_autotools_config -i -O--buildsystem=python_distutils
   dh_auto_configure -i -O--buildsystem=python_distutils
   dh_auto_build -i -O--buildsystem=python_distutils
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions

[... snipped ...]

testresources.tests.test_test_resource.TestTestResource.testFinishedWithMarksNonDirty
 ... ok
testresources.tests.test_test_resource.TestTestResource.testFinishedWithResetsCurrentResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetActivityForResourceWithExtensions
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetActivityForResourceWithoutExtensions
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceCallsMakeResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceDoesntDirty
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceIncrementsUses
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceResetsUsedResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceReturnsMakeResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceSetsCurrentResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testGetResourceTwiceReturnsIdenticalResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testInitiallyNoCurrentResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testInitiallyNotDirty 
... ok
testresources.tests.test_test_resource.TestTestResource.testInitiallyUnused ... 
ok
testresources.tests.test_test_resource.TestTestResource.testIsDirty ... ok
testresources.tests.test_test_resource.TestTestResource.testIsDirtyIsTrueIfDependenciesAreDirty
 ... ok
testresources.tests.test_test_resource.TestTestResource.testIsDirtyIsTrueIfDependenciesChanged
 ... ok
testresources.tests.test_test_resource.TestTestResource.testIsResetIfDependenciesAreDirty
 ... ok
testresources.tests.test_test_resource.TestTestResource.testRepeatedGetResourceCallsMakeResourceOnceOnly
 ... ok
testresources.tests.test_test_resource.TestTestResource.testResetActivityForResourceWithExtensions
 ... ok
testresources.tests.test_test_resource.TestTestResource.testResetActivityForResourceWithoutExtensions
 ... ok
testresources.tests.test_test_resource.TestTestResource.testResourceAvailableBetweenFinishedWithCalls
 ... ok
testresources.tests.test_test_resource.TestTestResource.testUnimplementedGetResource
 ... ok
testresources.tests.test_test_resource.TestTestResource.testUsedResourceResetBetweenUses
 ... ok
testresources.tests.test_test_resource.TestTestResource.testUsingTwiceMakesAndCleansTwice
 ... ok
testresources.tests.test_test_resource.TestTestResource.testneededResourcesClosure
 ... ok
testresources.tests.test_test_resource.TestTestResource.testneededResourcesDefault
 ... ok
testresources.tests.test_test_resource.TestTestResource.testneededResourcesDependenciesFirst
 ... ok
testresources.tests.test_test_resource.test_suite ... ok

==
FAIL: 

Processed: Downgrading the severity of DNS checks

[Debian Bug Tracking System]

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

> severity 835076 normal
Bug #835076 [src:python-glanceclient] python-glanceclient: accesses the 
internet during build
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#835076: Downgrading severity

[Thomas Goirand]

As per the discussion on debian-devel, I'm downgrading the severity of
this bug.

Cheers,

Thomas Goirand (zigo)

Bug#835700: marked as done (python-oauth2client: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Fri, 9 Sep 2016 10:29:51 +0200
with message-id <2877222d-46b6-64a5-937b-6ab481ae4...@debian.org>
and subject line Closing this bug too
has caused the Debian Bug report #835700,
regarding python-oauth2client: FTBFS: Tests failures
to be marked as done.

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

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


-- 
835700: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oauth2client
Version: 3.0.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> Traceback (most recent call last):
>   File "tests/test_service_account.py", line 80, in test_sign_blob
> private_key_id, signature = self.credentials.sign_blob('Google')
>   File "/<>/oauth2client/service_account.py", line 401, in 
> sign_blob
> return self._private_key_id, self._signer.sign(blob)
>   File "/<>/oauth2client/_openssl_crypt.py", line 97, in sign
> return crypto.sign(self._key, message, 'sha256')
>   File "/usr/lib/python2.7/dist-packages/OpenSSL/crypto.py", line 2563, in 
> sign
> md_ctx = _ffi.new("EVP_MD_CTX*")
> TypeError: cannot instantiate ctype 'EVP_MD_CTX' of unknown size
> 
> --
> Ran 539 tests in 4.575s
> 
> FAILED (SKIP=1, errors=31)
> debian/rules:29: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/08/28/python-oauth2client_3.0.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
For the same reason as the other related bugs, I'm closing this one: the
issue was in pyopenssl which was incompatible with the latest version of
python-cryptography. This was fixed since.

Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#775541: tests of new packages

[Andreas Henriksson]

Hello Vincent McIntyre.

Thanks for your thurough testing and useful feedback.

Let me start with a disclaimer: I'm not maintaining nfs (and I'm
not even using it myself so my knowledge is very limited). My only
involvement here is trying to squash some RC bugs and unblocking
work elsewhere by importing native systemd units.

On Fri, Sep 09, 2016 at 11:57:34AM +1000, Vincent McIntyre wrote:
> 
> Thanks Andreas for those new packages.
> I did some testing of the 1.2.8-9.2 packages on a clean jessie install.
> They are pretty close but I found an issue with NFS exports in one case.
> 
> I used the attached check.sh script to show the state of various targets
> as I changed things. The attached results.tar shows the output from it.
> Between each major stage below, the system is rebooted.
> Then I log in and run check.sh before doing anything else.
> Throughout, /etc/network/interfaces contained:
>   source /etc/network/interfaces.d/*
>   auto lo
>   iface lo inet loopback
>   allow-hotplug eth0

I think this  is problematic and unfortunately spoils my interest
in the rest of your testing.

>From what I've been told one of the main differences between "auto"
and "allow-hotplug" is that allow-hotplug will not block your bootup
so services will run wild and start up ASAP. This means they can and
likely will start up before your network connection is up. Specially
if using dhcp which takes time to configure the interface and extra
so if you're using a network device (eg. usb dongle) which takes a
long time to initialize.

I assume eth0 was involved in your tests, and if so it would be
very useful to know what difference it makes if you use auto
instead.

>   iface eth0 inet dhcp
> and /etc/network/interfaces.d/ was empty.
> 
> step 1 - jessie system with nfs packages 1.2.8-9
>  one fstab mount, no exports. no changes to /etc/default/nfs-*.
>  The fstab mount works ok; it tries to mount it way too early
>  but we invoke it with the 'bg' option so eventually it works.
> 
> step 2 - as above but with the _netdev option added to the fstab entry.
>  System still tries to mount too early, before dhclient is done,
>  but it works in the end.
> 
> step 3 - as above but export one filesystem.
>  The fstab mount works, as above.
>  Tried a few different ways to do the exports
>- wildcard host (step3.1)
>  This works ok.
>- point the export at a single host (step3.2)
>  This tries to start mountd to early, before it can resolve
>  the hostname given in the exports file.
>  As a result we end up with an empty export list:
>  # showmount -e
>  Export list for install:
>  #
>  Restarting the service once the system is fully booted works
>  # systemctl restart nfs-kernel-server.service
>  # showmount -e
>  Export list for install:
>  /data/INSTALL_1 mayhem.atnf.CSIRO.AU
>  #
>- point the export at a netgroup (step3.3)
>  This works, even though the netgroup cannot be resolved
>  (there's no definition for it).
>  # showmount -e
>  Export list for install:
>  /data/INSTALL_1 @all_hosts
>  #
> 
> NB nfs-kernel-server starts before dhclient
> Sep 08 17:04:46 install nfs-kernel-server[657]: Exporting directories for NFS 
> kernel daemon
> Sep 08 17:04:46 install kernel: NFSD: Using /var/lib/nfs/v4recovery as the 
> NFSv4 state recovery directory
> Sep 08 17:04:46 install kernel: NFSD: starting 90-second grace period (net 
> 818ba280)
> ...
> Sep 08 17:04:46 install rpc.mountd[738]: Version 1.2.8 starting
> Sep 08 17:04:46 install nfs-kernel-server[657]: Starting NFS kernel daemon: 
> nfsd mountd.
> Sep 08 17:04:46 install acpid[734]: starting up with netlink and the input 
> layer
> Sep 08 17:04:46 install acpid[734]: 1 rule loaded
> Sep 08 17:04:46 install acpid[734]: waiting for events: event logging is off
> ...
> Sep 08 17:04:49 install kernel: e1000e: eth0 NIC Link is Up 1000 Mbps Full 
> Duplex, Flow Control: None
> Sep 08 17:04:49 install kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
> becomes ready
> Sep 08 17:04:50 install dhclient[532]: DHCPDISCOVER on eth0 to 
> 255.255.255.255 port 67 interval 6
> ...
> Sep 08 17:04:56 install ifup[522]: Starting rpcbind (via systemctl): 
> rpcbind.service.
> Sep 08 17:04:56 install ifup[522]: Starting nfs-common (via systemctl): 
> nfs-common.service.
> Sep 08 17:04:56 install kernel: Key type dns_resolver registered
> Sep 08 17:04:56 install kernel: NFS: Registering the id_resolver key type
> Sep 08 17:04:56 install kernel: Key type id_resolver registered
> Sep 08 17:04:56 install kernel: Key type id_legacy registered
> 
> 
> step3.4 - install new nfs packages but don't reboot yet.
>   I didn't analyse this step carefully
> 
> step 4 - 

Processed: Bug#835247 marked as pending

[Debian Bug Tracking System]

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

> tag 835247 pending
Bug #835247 [src:python-wrapt] FTBFS against pytest 3.0.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#835247: marked as pending

[Thomas Goirand]

tag 835247 pending
thanks

Hello,

Bug #835247 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=openstack/python-wrapt.git;a=commitdiff;h=2db16e8

---
commit 2db16e88d618cc727b6d365a50b83f25f54e4555
Author: Thomas Goirand 
Date:   Fri Sep 9 08:10:09 2016 +

Using python$$pyvers -m pytest to run tests (Closes: #835247).

diff --git a/debian/changelog b/debian/changelog
index 33eaecd..72685f6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -8,6 +8,7 @@ python-wrapt (1.9.0-2) unstable; urgency=medium
   * Removed non-active maintainers.
   * Reviewed (build-)depends and ran wrap-and-sort -t -a.
   * Simplified debian/rules using goodies from openstack-pkg-tools >= 52~.
+  * Using python$$pyvers -m pytest to run tests (Closes: #835247).
 
  -- Thomas Goirand   Fri, 09 Sep 2016 08:05:11 +
 

Bug#836589: marked as done (icinga2: FTBFS on armhf/mips/mipsel)

[Debian Bug Tracking System]

Your message dated Fri, 09 Sep 2016 07:34:01 +
with message-id 
and subject line Bug#836589: fixed in icinga2 2.5.4-2
has caused the Debian Bug report #836589,
regarding icinga2: FTBFS on armhf/mips/mipsel
to be marked as done.

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

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


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

Hi,

Your package failed to build on armhf because of test suite errors,
and on mips/mipsel because of insuficient virtual memory.

Logs at https://buildd.debian.org/status/package.php?p=icinga2=unstable

Emilio

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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)
--- End Message ---
--- Begin Message ---
Source: icinga2
Source-Version: 2.5.4-2

We believe that the bug you reported is fixed in the latest version of
icinga2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated icinga2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 09 Sep 2016 08:59:57 +0200
Source: icinga2
Binary: icinga2 icinga2-common icinga2-bin icinga2-doc icinga2-classicui 
icinga2-ido-mysql icinga2-ido-pgsql icinga2-dbg libicinga2 icinga2-studio 
vim-icinga2
Architecture: source amd64 all
Version: 2.5.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Alexander Wirt 
Description:
 icinga2- host and network monitoring system
 icinga2-bin - host and network monitoring system - daemon
 icinga2-classicui - host and network monitoring system - classic UI
 icinga2-common - host and network monitoring system - common files
 icinga2-dbg - host and network monitoring system - debug symbols
 icinga2-doc - host and network monitoring system - documentation
 icinga2-ido-mysql - host and network monitoring system - MySQL support
 icinga2-ido-pgsql - host and network monitoring system - PostgreSQL support
 icinga2-studio - host and network monitoring system - studio API GUI
 libicinga2 - host and network monitoring system - internal libraries
 vim-icinga2 - syntax highlighting for Icinga 2 config files in VIM
Closes: 836589
Changes:
 icinga2 (2.5.4-2) unstable; urgency=medium
 .
   * [f749f15] Disable unity builds for arm
   * [33face7] Disable unity builds for mips and mipsel
 (Closes: #836589)
Checksums-Sha1:
 5fc59829ae62ed29cbbdfae6632bb9220f29244a 2887 icinga2_2.5.4-2.dsc
 d1a8d501519c452aaa4d30ad12ceafdecb46cf1b 30452 icinga2_2.5.4-2.debian.tar.xz
 8d7cb1532695507681b8c753b72aa4cdd789b670 91904 icinga2-bin_2.5.4-2_amd64.deb
 4ef9d07826a27a95b544827a3556b8e0dc8b69b5 60078 
icinga2-classicui_2.5.4-2_all.deb
 afac0943cf992c828c43ed685792a237103ef086 88938 icinga2-common_2.5.4-2_all.deb
 4d465573f61d0e57f9ffb0ebba707998993800ab 39537088 icinga2-dbg_2.5.4-2_amd64.deb
 310adb9f8a06ec5bbd0148618f4cde65f9e9cc18 280272 icinga2-doc_2.5.4-2_all.deb
 e9762c4a8119d8538fa2db326531142fcaf26b64 167590 
icinga2-ido-mysql_2.5.4-2_amd64.deb
 a80b665b2f48d45aff3908f2883f49580eb0ae13 159214 
icinga2-ido-pgsql_2.5.4-2_amd64.deb
 c8cf67f20053b4a707d32f0e9cf7fd746d25e26c 128646 
icinga2-studio_2.5.4-2_amd64.deb
 acc0239e938d2fc19ec563ba0ded54e6eef30451 51276 icinga2_2.5.4-2_amd64.deb
 a3ee3d1314ad7ea8d2e6576fc0dcd55b51d29ae3 2708166 libicinga2_2.5.4-2_amd64.deb
 914bc10bbe1c6b3d69417f771f2d8372aacd0d52 50812 vim-icinga2_2.5.4-2_all.deb
Checksums-Sha256:
 49860a85c05cbd31daf4d0a3f4de6b423313afa7f3a5cd046d05890d91c1e5a8 2887 
icinga2_2.5.4-2.dsc
 9de5fa797adc075f03b64799cc1d93857f3d15a8f33ac23b82b0abab1e76dcf2 

Bug#837136: libgtk3-perl: FTBFS: t/overrides.t failure

[Niko Tyni]

Package: libgtk3-perl
Version: 0.028-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

As noticed by ci.debian.net at
 http://ci.debian.net/packages/libg/libgtk3-perl/unstable/amd64/

this package fails its test suite on current sid, making it fail to
build from source.

  (overrides.t:10670): Gtk-WARNING **: Theme parsing error: :1:30: Using 
Pango syntax for the font: style pro
  perty is deprecated; please use CSS syntax
  :1:17not a number at /<>/blib/lib/Gtk3.pm line 968.
  # Looks like you planned 215 tests but ran 25.
  # Looks like your test exited with 25 just after 25.

-- 
Niko Tyni   nt...@debian.org

Bug#837133: libconfig-model-itself-perl: FTBFS: t/load_write_itself.t failure

[Niko Tyni]

Package: libconfig-model-itself-perl
Version: 2.005-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: autopkgtest

As noticed by ci.debian.net at
 http://ci.debian.net/packages/libc/libconfig-model-itself-perl/unstable/amd64/

this package fails its test suite on current sid, making it fail to
build from source.

  t/load_write_itself.t .. 
  1..8
  ok 1 - compiled
  ok 2 - Read Itself::Model and created instance
  ok 3 - Read all models from /usr/share/perl5/Config/Model
  ok 4 - dumped full tree in cds format
  Load command error:
  command: 'upstream_default=#'
  Syntax error: spurious char at command end: '=#'. Did you forget double 
quotes ?
  # Looks like you planned 8 tests but ran 4.
  # Looks like your test exited with 2 just after 4.
  Dubious, test returned 2 (wstat 512, 0x200)
  Failed 4/8 subtests 

-- 
Niko Tyni   nt...@debian.org

Bug#836384: closed by Jose Luis Rivero <jriv...@osrfoundation.org> (Bug#836384: fixed in ignition-transport 1.3.0-3)

[Gianfranco Costamagna]

control: reopen -1

Hi, can you please also make sure the testsuite works?

there is still the header file wrong include, I suspect nothing using this 
software can build in this way

autopkgtest [16:52:26]: test build: [---
Package ignition-msgs0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `ignition-msgs0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'ignition-msgs0', required by 'ignition-transport1', not found
igntest.c:1:33: fatal error: ignition/transport.hh: No such file or directory
#include 
^
compilation terminated.
autopkgtest [16:52:27]: test build: ---]
autopkgtest [16:52:27]: test build:  - - - - - - - - - - results - - - - - - - 
- - -
buildFAIL non-zero exit status 1
autopkgtest [16:52:27]: test build:  - - - - - - - - - - stderr - - - - - - - - 
- -
Package ignition-msgs0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `ignition-msgs0.pc'
to the PKG_CONFIG_PATH environment variable
Package 'ignition-msgs0', required by 'ignition-transport1', not found
igntest.c:1:33: fatal error: ignition/transport.hh: No such file or directory
#include 
^
compilation terminated.
autopkgtest [16:52:27]:  summary
buildFAIL non-zero exit status 1
Exit request sent.

This bad header is installed with ignition-transport

thanks,

G.




Il Giovedì 8 Settembre 2016 3:21, Debian Bug Tracking System 
 ha scritto:
This is an automatic notification regarding your Bug report
which was filed against the src:ignition-transport package:

#836384: ignition-transport: breaks with new protobuf3, and link failures

It has been closed by Jose Luis Rivero .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Jose Luis Rivero 
 by
replying to this email.


-- 
836384: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problemsSource: ignition-transport
Source-Version: 1.3.0-3

We believe that the bug you reported is fixed in the latest version of
ignition-transport, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 836...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated 
ignition-transport package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 06 Sep 2016 21:22:27 +
Source: ignition-transport
Binary: libignition-transport1 libignition-transport-dev
Architecture: source
Version: 1.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jose Luis Rivero 
Description:
libignition-transport-dev - Ignition Robotics transport Library - Development 
files
libignition-transport1 - Ignition Robotics Transport Library - Shared library
Closes: 836384
Changes:
ignition-transport (1.3.0-3) unstable; urgency=medium
.
   * Added patch for pkgconfig file
(Closes: #836384)
Checksums-Sha1:
ad51c8c4fc5fc314d58235cd970dcd9ba6b3e312 2026 ignition-transport_1.3.0-3.dsc
e6aa6bf38cffde7ecd9a13ee0b115cb0131a7c0a 5856 
ignition-transport_1.3.0-3.debian.tar.xz
Checksums-Sha256:
c26a5af1431dde2267eee8439126e88186fd5611727119e3f31aae1557409d1d 2026 
ignition-transport_1.3.0-3.dsc
f04675d9322581875d1643d40b010ab8821825ceb76718dde8f93831437e2fed 5856 
ignition-transport_1.3.0-3.debian.tar.xz
Files:
c82545c34494bf902c881fe5fdc5cccf 2026 science extra 
ignition-transport_1.3.0-3.dsc
41614dc7aee170587c927d4fa6e9 5856 science extra 
ignition-transport_1.3.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCgAGBQJX0LdpAAoJEF6UbAkK/wQnJEEIAJ/JPQitgAjVvmV121ei86JJ
ZMBoafAM1FTnKaXOhyc/Jqe7OnhIalvqTnsaNpLOAJ94nn/aHWQuPRS9Do5pcTwG
d+ftbw6zR7uQxB3gE3c2PUhjaUjN3LEPFhs8ZrdNrtVXSIhm9PGVzlI/RJ3zVeWA
Mo27xkuK5awm6HBtoMvy/yDeL545cqKZnkGrFmH4ZvaOmw/dqU1IE+QGhneEVGj4
L07nSEaJh6ntdAO8kcLiJRBRcOfz85PZYMKjHYEF9xSuZOllQpB5QDnft37l+wj+
uHTGVCJqtkrCIvveDTN8Yfk9kqyg8hP5tGpea09P2gseN7K2HenFL18wnB/1Hh4=
=R2T8
-END PGP SIGNATURE-
Source: ignition-transport
Version: 1.3.0-2
Severity: serious

Hi, the latest protobuf3 broke ignition-transport testsuite and package, lets 
analyze the issues:
(based on 

Processed: Re: Bug#836384 closed by Jose Luis Rivero <jriv...@osrfoundation.org> (Bug#836384: fixed in ignition-transport 1.3.0-3)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #836384 {Done: Jose Luis Rivero } 
[src:ignition-transport] ignition-transport: breaks with new protobuf3, and 
link failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ignition-transport/1.3.0-3.

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