Bug#823788: marked as done (sbuild: non-error on stderr: "There are no foreign architectures configured")

[Debian Bug Tracking System]

Your message dated Thu, 12 May 2016 05:49:18 +
with message-id 
and subject line Bug#823788: fixed in sbuild 0.69.0-2
has caused the Debian Bug report #823788,
regarding sbuild: non-error on stderr: "There are no foreign architectures 
configured"
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.)


-- 
823788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sbuild
Version: 0.69.0-1
Severity: normal


Hi!
I'm afraid that today's update introduced a spurious message, emitted both
on package build and on chroot update:
"There are no foreign architectures configured".

Putting aside the question whether this message fits places it's emitted, it
definitely shouldn't be written to stderr.  This breaks scripts that assume
stderr output means errors.  This includes for example cronjobs to update
chroots.


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

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

Versions of packages sbuild depends on:
ii  adduser 3.114
ii  apt-utils   1.2.11
ii  libsbuild-perl  0.69.0-1
ii  perl5.22.2-1

Versions of packages sbuild recommends:
ii  debootstrap  1.0.81
ii  fakeroot 1.20.2-1

Versions of packages sbuild suggests:
pn  deborphan  
ii  wget   1.17.1-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sbuild
Source-Version: 0.69.0-2

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

Debian distribution maintenance software
pp.
Johannes Schauer  (supplier of updated sbuild 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, 12 May 2016 07:36:32 +0200
Source: sbuild
Binary: libsbuild-perl sbuild buildd
Architecture: source
Version: 0.69.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian buildd-tools Developers 

Changed-By: Johannes Schauer 
Description:
 buildd - Daemon for automatically building Debian binary packages from Deb
 libsbuild-perl - Tool for building Debian binary packages from Debian sources
 sbuild - Tool for building Debian binary packages from Debian sources
Closes: 823788 823897
Changes:
 sbuild (0.69.0-2) unstable; urgency=medium
 .
   * add patch 0001-lib-Sbuild-ResolverBase.pm-do-not-produce-non-error-.patch
 to make sbuild not print on stderr during sbuild-update unless it is an
 error (closes: #823788)
   * 0001-bin-sbuild-createchroot-fix-chown-chmod-error-checks.patch which
 fixes error checking of chown and chmod calls in sbuild-createchroot
 (closes: #823897)
Checksums-Sha1:
 512619994d852b5a53003e8901151770c3b24774 2236 sbuild_0.69.0-2.dsc
 798e24a4ba837ba2a0ef243258e7f403307b18b5 54232 sbuild_0.69.0-2.debian.tar.xz
Checksums-Sha256:
 bc9bb4af2935bf88d10aa6d236b38b0d1b1554a6f7b182bf3a0a7c6b74f10cbe 2236 
sbuild_0.69.0-2.dsc
 82c11022a1a69e249939290fbce774567b4f6c82db0b857dc0670efa4cdd0b8f 54232 
sbuild_0.69.0-2.debian.tar.xz
Files:
 3ee356a4878438ca6abe15fd4467ccb3 2236 devel extra sbuild_0.69.0-2.dsc
 e94093b80c7582a3e197d2ee500417b3 54232 devel extra 
sbuild_0.69.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJXNBbMAAoJEPLLpcePvYPhEpsQAJ9K1U8v6VJOOpjIkrieTjVw
CaafmiVUvqSWdnyLJwX3jW5w0mjXnLZpD43Dgk08NnLmFBGpJzB0rk7glRKdUhcX
0xXdnPf+VuJHdIskeLGAOCZ4c/esnLauqfgrR7gKxaXczxbZvJUIbzsQT5amoKYn
+4IC+v2Up3RrOPa8jjon4qUs2s+NQ4Zy7IbROYVYgz7PbQN8pGTKz5bmqaSOWtW8
rp8XPmCeQuPmRH4pvej95BB4XoTTyJnpX8V7ZTs7t2wCgYrxxo5QPZKEPuBA6XZj
tH4MAGgMAF/trFRnsaBVsc9o3ym3c5ciY2QiPbb5G4B1G7m54EpjzLHwTvP+x0Ba
QFv9Wt1GzZ027zZ5nXI28rRthSahZzbbvzhqr0JRr63oMDee5xUtaBkMNzJfmT+O

Processed: fixed 824039 in 20120731.b-7.2

[Debian Bug Tracking System]

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

> fixed 824039 20120731.b-7.2
Bug #824039 {Done: Fabian Greffrath } [fontforge] fontforge: 
symbol lookup error:
Marked as fixed in versions fontforge/20120731.b-7.2; no longer marked as fixed 
in versions 20120731.b-7.2.
> thanks
Stopping processing here.

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

Bug#824083: cbds 0.4.131 makes glib2.0 FTBFS: /usr/share/cdbs/1/class/gnome.mk:38: recipe for target 'clean' failed

[Helmut Grohne]

Package: cdbs
Version: 0.4.131
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:glib2.0

Hi Jonas,

It looks like your 0.4.131 upload breaks src:glib2.0. You can find a
(native) build log attached. The gist seems to be:

| /usr/share/cdbs/1/class/gnome.mk:38: recipe for target 'clean' failed
| make: *** [clean] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2

I'm not sure whether this issue is in glib2.0 or cdbs. Feel free to move
it if appropriate.

Helmut


glib2.0_2.48.1-1_amd64-20160512-0554.build.xz
Description: application/xz

Processed: cbds 0.4.131 makes glib2.0 FTBFS: /usr/share/cdbs/1/class/gnome.mk:38: recipe for target 'clean' failed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:glib2.0
Bug #824083 [cdbs] cbds 0.4.131 makes glib2.0 FTBFS: 
/usr/share/cdbs/1/class/gnome.mk:38: recipe for target 'clean' failed
Added indication that 824083 affects src:glib2.0

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

Bug#823881: dosfstools: mmd fails right after mkfs.msdos (sectors/tracks mismatch)

[Andreas Bombe]

On Wed, May 11, 2016 at 05:32:17AM +0200, Cyril Brulebois wrote:
> [ Poke Steve. ]
> 
> Andreas Bombe  (2016-05-11):
> > On Tue, May 10, 2016 at 02:15:42PM +0200, Andreas Bombe wrote:
> > > Since 416 blocks is a rather odd value, the default is used and that has
> > > changed. I think mtools is overzealous in checking those values and
> > > refusing to work. Still, it probably makes sense to use 64/32 as the
> > > default for smaller filesystem sizes (up to 512 MB possibly) and I'll
> > > prepare a version that implements this.
> > 
> > Uploading this now.
> > 
> > As far as I'm concerned, I consider this an aesthetic change. There is
> > still no guarantee that the total number of sectors is a multiple of
> > sectors per track. It just happens to work with the current values.
> 
> Steve → we probably don't want to be hardcoding such things in so many
> places right? 3 calls in src:debian-installer, plus debian-cd, and maybe
> others?

In my opinion all that effort to placate mtools is the quintessential
tail wagging the dog. I don't know the installer environment, but
disabling those checks in /etc/mtools.conf or ~/.mtoolsrc would be the
way to go.

> > If you want to make this robust, you'll either have to explicitly
> > specify matched size/sectors/heads on the command line to mkfs.msdos or
> > disable the bogus mtools check like everyone else does when encountering
> > that error.
> 
> Thanks for your input and the proposed change.
> 
> I think Steven mentioned (when we first diagnosed this) a possibly
> bogus/overzealous check on mtools side as well. You seem to agree. So,
> if this check is bogus, why not fix it/remove it upstream then?

Upstream for mtools does not seem to be particularly active, last
release was in 2013.

The problem with this check is that it is at best a heuristic. Total
sectors not being a multiple of sectors per track means that some
sectors in the last track are left unused. And nobody would just waste
some of the scarce space on a floppy, right?

That might indicate something is fishy, but it's not an actual error.
It's definitely meaningless in the linear addressing case of larger
disks where the 255/63 dummy values are used.

> > Seriously, searching for that error message in your favorite search
> > engine will give you pages upon pages of hits, all of them describing
> > how to turn it off.
> 
> Seriously, I read the man^Winfo page and implemented a workaround in
> src:debian-installer already.

I didn't mean to come across as sarcastic or whatever, I just wanted to
note how there are so many people affected by this while I couldn't find
anyone treating it as anything but a nuisance error. So yeah, the
consensus seems to be it's a bogus check.


Andreas

Bug#824082: r-cran-tm: missing dependencies on r-cran-nlp and r-cran-slam

[Evan Thompson]

Package: r-cran-tm
Version: 0.6-2-2
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

When attempting to load tm in R:

> library(tm)
Error: package ‘NLP’ required by ‘tm’ could not be found

Installing r-cran-nlp solves this first issue, but then:

> library(tm)
Loading required package: NLP
Error in loadNamespace(i, c(lib.loc, .libPaths()), versionCheck = vI[[i]]) :
  there is no package called ‘slam’
Error: package or namespace load failed for ‘tm’

Installing r-cran-slam solves the second issue.

Regards,
-- Evan Thompson



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

Kernel: Linux 4.5-3.dmz.2-liquorix-amd64 (SMP w/4 CPU cores; PREEMPT)
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 r-cran-tm depends on:
ii  libc6  2.22-7
ii  r-base-core [r-api-3]  3.3.0-1

r-cran-tm recommends no packages.

r-cran-tm suggests no packages.

-- no debconf information

Bug#823316: marked as done (stk: contains non-free Steinberg ASIO library)

[Debian Bug Tracking System]

Your message dated Thu, 12 May 2016 01:22:23 +
with message-id 
and subject line Bug#823316: fixed in stk 4.5.2+dfsg-1
has caused the Debian Bug report #823316,
regarding stk: contains non-free Steinberg ASIO library
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.)


-- 
823316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stk
Version: 4.4.3-2
Severity: serious

Hi,

stk contains a bundled copy of the Steinberg ASIO library headers in
src/include. These files are under very strict licensing terms which
can be found here (you have to download the SDK and open the PDF):
http://www.steinberg.net/en/company/developers.html

The term "Licensed Software Developer Kit" appears to cover all the
code:

1.1
The object of this agreement consists of the Steinberg ASIO (Audio
Stream I/O) Software Development Kit version 2.3, respectively any
preview version of this Kit, comprising of documentation, example code,
and several ASIO examples. These are described hereinafter as the
"Licensed Software Developer Kit".

The license goes on to include other terms which seem to prohibit
modification or redistribution in most cases:

2.3
The Licensee has no permission to sell, license, give-away and/or
distribute the Licensed Software Developer Kit or parts of it for the
use as software developer kit in any way, for example, integrated in
any framework application, on any medium, including the Internet, to
any other person, including sub-licensors of the Licensee or companies
where the Licensee has any involvement. This includes re-working this
specification, or reverse-engineering any products based upon this
specification.

2.4
In case the Licensed Software Developer Kit is modified, it shall not
be published, sold or distributed without agreement of Steinberg.
Furthermore, the naming of the Licensed Software Developer Kit shall
not include “ASIO 2.3 SDK” or any combination containing the VST brand
without permission of Steinberg.

Thanks,
James

signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: stk
Source-Version: 4.5.2+dfsg-1

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated stk 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: Wed, 11 May 2016 21:25:54 -0300
Source: stk
Binary: libstk0-dev libstk-4.5.0 stk stk-doc
Architecture: source
Version: 4.5.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Felipe Sateler 
Description:
 libstk-4.5.0 - Sound Synthesis Toolkit
 libstk0-dev - Sound Synthesis Toolkit (development files)
 stk- Sound Synthesis Toolkit (example applications)
 stk-doc- Sound Synthesis Toolkit (documentation)
Closes: 823316
Changes:
 stk (4.5.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
 - Repack, add asio files to Files-Excluded. Closes: #823316
 - Drop 0006-Install-missing-include-files-SKINI.msg-and-SKINI.tb.patch, 
not needed anymore
   * Add upstream patch to fix SKINI renaming
   * Build doxygen docs on -indep targets.
Checksums-Sha1:
 e4689e05c107baded526dc654ce281f8cf4c094e 2351 stk_4.5.2+dfsg-1.dsc
 cbb0ff47835ee06e237da7a8986b3077d3d49880 1125351 stk_4.5.2+dfsg.orig.tar.gz
 4284a365b565273fa6f86010e0a4e4cf142a13c6 13928 stk_4.5.2+dfsg-1.debian.tar.xz
Checksums-Sha256:
 a713148b7e52409ee53c1e37ded9a3e2c55e395d99fa40692085d756f1f26f60 2351 
stk_4.5.2+dfsg-1.dsc
 f4deea0f6997a13d7369ec9743450862d98895c664b6b4b881e041cb69225ed4 1125351 
stk_4.5.2+dfsg.orig.tar.gz
 4cfae8842d78160134b32d29fb5d87b03b3a92a13cd84f6c6374af6b5eb5b2ae 13928 
stk_4.5.2+dfsg-1.debian.tar.xz
Files:
 186a3991fb45a65f54029fc3e0e62073 2351 sound optional stk_4.5.2+dfsg-1.dsc
 7072165f79755e0d096baf744fb6a8d0 

Bug#824068: sympytexpackage: documentation is non-free

[Norbert Preining]

Hi Francesco,

> The Creative Commons Attribution-NonCommercial-ShareAlike v3.0 license

Indeed, thanks. I have contacted the author as well as TeX Live upstream.
Either it will be relicened or we remove it from TeX Live (upstream)
and then also from Debian.

Thanks

Norbert


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

Bug#823316: marked as pending

[Felipe Sateler]

tag 823316 pending
thanks

Hello,

Bug #823316 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/stk.git;a=commitdiff;h=6718001

---
commit 671800129a61cc2d5326f146b286a5605d96481e
Author: Felipe Sateler 
Date:   Wed May 11 21:26:04 2016 -0300

Release to unstable

diff --git a/debian/changelog b/debian/changelog
index 94d39ee..e92511d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+stk (4.5.2+dfsg-1) unstable; urgency=medium
+
+  * New upstream release
+- Repack, add asio files to Files-Excluded. Closes: #823316
+- Drop 0006-Install-missing-include-files-SKINI.msg-and-SKINI.tb.patch, 
not needed anymore
+  * Add upstream patch to fix SKINI renaming
+  * Build doxygen docs on -indep targets.
+
+ -- Felipe Sateler   Wed, 11 May 2016 21:25:54 -0300
+
 stk (4.5.0-3) unstable; urgency=medium
 
   * Use autotools_dev again to get up-to-date config.{sub,guess}

Processed: Bug#823316 marked as pending

[Debian Bug Tracking System]

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

> tag 823316 pending
Bug #823316 [src:stk] stk: contains non-free Steinberg ASIO library
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#824074: gimp: Crashes (apparently) when Caps Lock key is pressed

[Ari Pollak]

Since I'm unable to reproduce this on my system, could you please get a
backtrace by installing the gimp-dbg package and following the directions
here: https://wiki.debian.org/HowToGetABacktrace

Bug#823809: marked as done (yosys: FTBFS in testing)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 22:42:53 +
with message-id 
and subject line Bug#823809: fixed in yosys 0.6-6
has caused the Debian Bug report #823809,
regarding yosys: FTBFS in testing
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.)


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

Dear maintainer:

This package fails to build from source in stretch:


frontends/ast/ast.cc: In member function 'Yosys::RTLIL::Const 
Yosys::AST::AstNode::realAsConst(int)':
frontends/ast/ast.cc:860:17: error: 'isfinite' was not declared in this scope
  if (!isfinite(v)) {
 ^
frontends/ast/ast.cc:860:17: note: suggested alternative:
In file included from /usr/include/c++/5/random:38:0,
 from /usr/include/c++/5/bits/stl_algo.h:66,
 from /usr/include/c++/5/algorithm:62,
 from ./kernel/yosys.h:47,
 from frontends/ast/ast.cc:29:
/usr/include/c++/5/cmath:601:5: note:   'std::isfinite'
 isfinite(_Tp __x)
 ^
Makefile:340: recipe for target 'frontends/ast/ast.o' failed


The error seems related to #822408.

Note: If you need some -dev package which is only available in
unstable for now, consider using a versioned build-depends.
This will not prevent the package from propagating to testing
but at least everybody will know why it does not build.

The full build log is attached.

Thanks.

yosys_0.6-5_amd64-20160509-1144.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: yosys
Source-Version: 0.6-6

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

Debian distribution maintenance software
pp.
Ruben Undheim  (supplier of updated yosys 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: Wed, 11 May 2016 22:20:00 +0200
Source: yosys
Binary: yosys yosys-dev yosys-doc
Architecture: source
Version: 0.6-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ruben Undheim 
Description:
 yosys  - Framework for Verilog RTL synthesis
 yosys-dev  - Framework for Verilog RTL synthesis (development files)
 yosys-doc  - Documentation for Yosys
Closes: 823809
Changes:
 yosys (0.6-6) unstable; urgency=medium
 .
   * Added versioned build-dependency on gcc-5 (>= 5.3.1-15) since it
 now fails to build with older versions due to the fix for #822408.
 (Closes: #823809)
   * Updated Standards to 3.9.8 - no changes
Checksums-Sha1:
 b5ab988f2383b6c2687476428bc2b4febc1fa217 2457 yosys_0.6-6.dsc
 d44205fc3b8f4f67365efb8ff10e5c06976362ce 13016 yosys_0.6-6.debian.tar.xz
Checksums-Sha256:
 e8a2935397b0f1943b77a72f51ca6913e3f7de862789d222aa08a54608668e37 2457 
yosys_0.6-6.dsc
 87a6b25bd5d98760750486162dc682ca7e030d9819bf590999e8167d9245ae44 13016 
yosys_0.6-6.debian.tar.xz
Files:
 313c7d940afecccd24ba1cf6a257fcb9 2457 electronics optional yosys_0.6-6.dsc
 ab0e6bdff767fa443a828c3813fba59e 13016 electronics optional 
yosys_0.6-6.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJXM5W1AAoJEPxqH2TRCNERfLsQAN1iCSyp2tGm7v/6ylGPIoFk
xlYQNz/GUD9nAXDHLczY3G5xvFu+8BZrPMx+lVTVJ1WI3Vg2WgjKD0t9K6GjdmWn
V2VMwx6wFz4UlDSwJYpBaRyTYj0GqMvtp9nDT4ZEi7C5AjSrIXbjgrwH/wzLkud3
H3sxltgiIrQrbPk4E/7GAaTo7E6KCGjY9ZUmR2tT0h/3amfzVt0S2dAjQlnar8un
24zh4ndufPHTOv0GWrY97eYWU4sT7ysd8lewUycSZ3lFrhebIk/hYSMZy29Xo2rm
KXHpswmGE7nb/BiSJCxvqJB1dCQ+am9nruORyuvll+kiRjEeMc5T+aJLKdv7Mh7Q
MEMyu1CVx+qZX1D5RKL3HBXr011D86MJHAC2UA2dE5bAMfScwwnX+2b+3kmhjOKv
DnjDDG1QbuXICJyLWkvxbOL0D9wWUkx9IIXnyFYjceTqk8vBJyVQTfr2eqLQdHsi
/L/Kty+wlhyHTxqOu+NHbY40EyfUjSaJeS8e2mnSRCuQPbJtVVSUMlfM4uU0gXsN

Bug#823780: marked as done (sks fails to start)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 22:40:03 +
with message-id 
and subject line Bug#823780: fixed in sks 1.1.5-7
has caused the Debian Bug report #823780,
regarding sks fails to start
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.)


-- 
823780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sks
Version: 1.1.5-5
Severity: grave
Justification: renders package unusable


Hi.

Since the recent upgrade to -5, sks no longer starts, bailing out
with:
May 08 22:46:58 kronecker systemd[1]: Started SKS database service.
May 08 22:46:58 kronecker systemd[1]: Started SKS reconciliation service.
May 08 22:46:58 kronecker sks[4855]: 2016-05-08 22:46:58 sks_db, SKS version 
1.1.5+
May 08 22:46:58 kronecker sks[4855]: 2016-05-08 22:46:58 Using BerkelyDB 
version 5.3.28
May 08 22:46:58 kronecker sks[4855]: 2016-05-08 22:46:58 Copyright Yaron Minsky 
2002, 2003, 2004
May 08 22:46:58 kronecker sks[4855]: 2016-05-08 22:46:58 Licensed under GPL. 
See LICENSE file for details
May 08 22:46:58 kronecker sks[4855]: 2016-05-08 22:46:58 http port: 11371
May 08 22:46:58 kronecker sks[4855]: Fatal error: exception Failure("Failure 
while binding socket.  Probably another socket bound to this address")
May 08 22:46:58 kronecker systemd[1]: sks.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
May 08 22:46:58 kronecker systemd[1]: sks.service: Unit entered failed state.
May 08 22:46:58 kronecker systemd[1]: sks.service: Failed with result 
'exit-code'.
May 08 22:46:58 kronecker sks[4856]: Fatal error: exception Failure("Failure 
while binding socket.  Probably another socket bound to this address")
May 08 22:46:58 kronecker systemd[1]: sks-recon.service: Main process exited, 
code=exited, status=2/INVALIDARGUMENT
May 08 22:46:58 kronecker systemd[1]: Stopped SKS reconciliation service.
May 08 22:46:58 kronecker systemd[1]: sks-recon.service: Unit entered failed 
state.
May 08 22:46:58 kronecker systemd[1]: sks-recon.service: Failed with result 
'exit-code'.


However, nothing binds on that:
# netstat --inet --inet6 -pln | grep 1137
tcp0  0 1.2.3.4:11371 0.0.0.0:*LISTEN  
4895/apache2
tcp6   0  0 11:22:33:44::11371 :::*LISTEN  
4895/apache2
tcp6   0  0 11:22:33:44::11371 :::*LISTEN  
4895/apache2
and even with stopping apache it doesn't start.
# netstat --inet --inet6 -pln | grep 1137
#


Cheers,
Chris.

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: sks
Source-Version: 1.1.5-7

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated sks 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: Wed, 11 May 2016 11:10:21 -0400
Source: sks
Binary: sks
Architecture: source
Version: 1.1.5-7
Distribution: unstable
Urgency: medium
Maintainer: Christoph Martin 
Changed-By: Daniel Kahn Gillmor 
Description:
 sks- Synchronizing OpenPGP Key Server
Closes: 705725 750504 778726 823780 823781
Changes:
 sks (1.1.5-7) unstable; urgency=medium
 .
   * re-include stock files in /var/lib/sks/www
   * fix typo in example config file.
 .
 sks (1.1.5-6) unstable; urgency=medium
 .
   * ship useful helper scripts: sks-db-setup and sks-db-upgrade
   * drop ancient tests in postinst, improve logic, and simplify by using
 sks-db-upgrade
   * avoid recursive chowns (Closes: #705725)
   * sks-db-upgrade will not fail when database or log files are 

Bug#822489: marked as done (armhf ABI detection crashing ldconfig on arm64)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 22:29:02 +
with message-id 
and subject line Bug#822489: fixed in glibc 2.22-8
has caused the Debian Bug report #822489,
regarding armhf ABI detection crashing ldconfig on arm64
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.)


-- 
822489: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822489
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libc6-bin
Severity: serious
Version: 2.22-7
Tags: patch

Hi folks,

Steev has reported some crashing using ldconfig on arm64 systems with
armhf added as a secondary architecture - he's using this config in
Kali, for example.

Working through the problem with him on #debian-arm, I can see that
it's a problem with our/my patch for ARM ABI detection. On older
binaries that predate the new ABI flags in the ELF header, we're still
parsing the ARM attributes. That works fine on armel/armhf, but on
arm64 this code is being built wrongly using native (ELF64)
types. This patch is the obvious fix - enforce using ELF32 types for
all arches.

It seems that we still have some older packages without the ABI flags
attached - libshout3 is one such. :-(

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"I can't ever sleep on planes ... call it irrational if you like, but I'm
 afraid I'll miss my stop" -- Vivek Das Mohapatra
--- debian/patches/arm/unsubmitted-ldconfig-cache-abi.diff~	2016-04-19 09:49:50.0 +
+++ debian/patches/arm/unsubmitted-ldconfig-cache-abi.diff	2016-04-24 23:12:33.808037225 +
@@ -40,8 +40,8 @@
 +static int is_library_hf(const char *file_name, void *file_contents, size_t file_length)
 +{
 +  unsigned int i;
-+  ElfW(Ehdr) *ehdr = (ElfW(Ehdr) *) file_contents;
-+  ElfW(Shdr) *shdrs;
++  Elf32_Ehdr *ehdr = (Elf32_Ehdr *) file_contents;
++  Elf32_Shdr *shdrs;
 +
 +  shdrs = file_contents + ehdr->e_shoff;
 +  for (i = 0; i < ehdr->e_shnum; i++)
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.22-8

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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: Wed, 11 May 2016 23:39:05 +0200
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 
libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 
libc6-dev-x32 libc6-xen libc6.1-alphaev67
Architecture: source
Version: 2.22-8
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: Development binaries
 libc-l10n  - GNU C Library: localization files
 libc0.1- GNU C Library: Shared libraries
 libc0.1-dbg - GNU C Library: detached debugging symbols
 libc0.1-dev - GNU C Library: Development Libraries and Header Files
 libc0.1-dev-i386 - GNU C Library: 32bit development libraries for AMD64
 libc0.1-i386 - GNU C Library: 32bit shared libraries for AMD64
 libc0.1-pic - GNU C Library: PIC archive library
 libc0.1-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3- GNU C Library: Shared libraries
 libc0.3-dbg - GNU C Library: detached debugging symbols
 libc0.3-dev - GNU C Library: Development Libraries 

Bug#816076: wicd-daemon: upgrade reconfigures static ethernet interface, and kills ssh sessions.

[Vincent Lefevre]

Hi,

On 2016-04-20 21:05:47 +1000, Andrew Vaughan wrote:
> On 20 April 2016 at 19:58, Vincent Lefevre  wrote:
> > Probably the same bug as bug 557156 (from 2009!). The problem is that
> > wicd-daemon tries to reconfigure the ethernet interface even though
> > it is configured not to connect to it automatically (which should be
> > and is the default). A workaround is to remove eth0 from the wicd
> > configuration.

Concerning the problem I had, it was apparently a documentation bug.
I've submitted a patch for the wicd-manager-settings.conf(5) man page.

> As far as I am aware, I have never touched the wicd config files.  And a
> package shouldn't ship with a config that will break an otherwise valid
> configuration belonging to a different package on package upgrade.

The problem in your case was that you managed eth0 with both ifupdown
and wicd, which is obviously wrong. I thought that the default
configuration instructed that the wired interface wasn't managed
by default, but this was the documentation bug. If an interface
name is provided, then it will be managed by wicd automatically.

IMHO, the default config file should be written in such a way that
a wired interface is not managed by wicd because it could already
be managed in some other way. Unfortunately the usual choice is to
configure things at much as possible even though this may be broken
(for instance, just after installing postfix, a daemon is started
with a basic config file that rejects received mail, which is really
bad when re-installing a machine).

If the default config file isn't changed, recommending wicd is wrong,
IMHO.

If the wired interface is deconfigured during a wicd upgrade, this is
also wrong, as this can break upgrade via SSH.

> Now for the new stuff.  Today I removed wicd and related packages.
> I'm pretty sure I purged the config files.  To cut a long story short,
> purging wicd and related packages resulted in eth0 having it's IPv4
> address removed.  Eth0 was still up with a IPv6 address.  But the
> machine was no longer reachable over IPv4.  Probably just a
> different variant of the same underlying buggy behaviour.

I think that if the wired interface is managed by wicd, then it makes
sense to deconfigure it when purging wicd (and even just removing it),
because the interface wouldn't be controlled in any way, with no
possibility of clean-up.

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

Bug#824074: gimp: Crashes (apparently) when Caps Lock key is pressed

[Guillermo]

Package: gimp
Version: 2.8.16-1+b1
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

While on a normal usage of Gimp sometimes it crashes losing all unsaved 
progress. Apparently this happens after pressing the Caps Lock key, but not 
always.

Here's the output of when the issue happens:

lcms: skipping conversion because profiles seem to be equal:
 sRGB IEC61966-2.1
 sRGB built-in

(gimp:23986): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 
'instance != NULL && instance->g_class != NULL' failed

(gimp:23986): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 
'instance != NULL && instance->g_class != NULL' failed

(script-fu:23995): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
Violación de segmento (Spanish for 'segmentation fault')


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

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

Versions of packages gimp depends on:
ii  gimp-data2.8.16-1
ii  libaa1   1.4p5-44
ii  libatk1.0-0  2.20.0-1
ii  libbabl-0.1-01:0.1.16-dmo1
ii  libbz2-1.0   1.0.6-8
ii  libc62.22-7
ii  libcairo21.14.6-1+b1
ii  libdbus-1-3  1.10.8-1
ii  libdbus-glib-1-2 0.106-1
ii  libexif120.6.21-2
ii  libexpat12.1.1-1
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libgegl-0.3-01:0.3.6-dmo4
ii  libgimp2.0   2.8.16-1+b1
ii  libglib2.0-0 2.48.0-1
ii  libgs9   9.19~dfsg-1+b1
ii  libgtk2.0-0  2.24.30-1.1
ii  libgudev-1.0-0   230-3
ii  libice6  2:1.0.9-1+b1
ii  libjasper1   1.900.1-debian1-2.4+deb8u1
ii  libjpeg62-turbo  1:1.4.2-2
ii  libjson-glib-1.0-0   1.2.0-1
ii  liblcms2-2   2.7-1
ii  libmng1  1.0.10+dfsg-3.1+b3
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpangoft2-1.0-01.40.1-1
ii  libpng16-16  1.6.21-4
ii  libpoppler-glib8 0.38.0-3
ii  librsvg2-2   2.40.15-1
ii  libsm6   2:1.2.2-1+b1
ii  libtiff5 4.0.6-1
ii  libwmf0.2-7  0.2.8.4-10.5+b1
ii  libx11-6 2:1.6.3-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.1-2+b2
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.11-1+b1
ii  libxt6   1:1.1.5-1
ii  python-gtk2  2.24.0-4
ii  python2.72.7.11-8
pn  python:any   
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages gimp recommends:
ii  ghostscript  9.19~dfsg-1+b1

Versions of packages gimp suggests:
pn  gimp-data-extras  
pn  gimp-help-en | gimp-help  
ii  gvfs-backends 1.28.1-1
ii  libasound21.1.0-1

-- no debconf information

Bug#824068: sympytexpackage: documentation is non-free

[Francesco Poli (wintermute)]

Package: texlive-math-extra
Version: 2015.20160320-1
Severity: serious
Justification: Policy 2.2.1

Hello and thanks for maintaining TeX Live in Debian!

I noticed that binary package texlive-math-extra includes, among
other LaTeX packages, sympytexpackage. This is very useful, thanks
for including it!

However, there's a licensing issue: although the sympytexpackage
LaTeX package and associated Python module are distributed under
the terms of the GNU GPL v2 or later, the documentation for
sympytexpackage is distributed under the terms of the CC-by-sa-nc
v3.0, as explained at the end of
/usr/share/doc/texlive-doc/latex/sympytexpackage/README
and in section 7 of
/usr/share/doc/texlive-doc/latex/sympytexpackage/sympytexpackage.pdf

The Creative Commons Attribution-NonCommercial-ShareAlike v3.0 license
is not acceptable for Debian main.

Please persuade the sympytexpackage author (Tim Molteno) to re-license
the documentation under the same terms as the rest of the
sympytexpackage LaTeX package (GNU GPL v2 or later).
If this attempt fails, please drop the non-free documentation from
the Debian package (of course, I would strongly prefer seeing
the documenation re-licensed under DFSG-free terms, rather than
dropped!).

Thanks for your time!
Bye.

Bug#824048: Any change in blastp? (Was: Bug#824048: python-biopython: FTBFS: AssertionError: 10 != 1)

[Andreas Tille]

On Wed, May 11, 2016 at 05:35:27PM +0100, Chris Lamb wrote:
> ...
>   Bio.PDB.Selection docstring test ... ok
>   ==
>   FAIL: test_blastp (test_NCBI_BLAST_tools.Pairwise)
>   Pairwise BLASTP search
>   --
>   Traceback (most recent call last):
> File 
> "/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/Tests/test_NCBI_BLAST_tools.py",
>  line 103, in test_blastp
>   self.assertEqual(10, stdoutdata.count("Query= "))
>   AssertionError: 10 != 1
>   
>   --
>   Ran 228 tests in 101.627 seconds
>   
>   FAILED (failures = 1)

Does any body know about a recent change in blastp?

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#804531: eagle: cannot be rebuilt against libssl1.0.2

[Scott Howard]

On Wed, May 11, 2016 at 7:23 AM, Sebastian Andrzej Siewior
 wrote:
> On 2016-05-10 18:19:02 [-0400], Scott Howard wrote:
>> I agree with this assessment. I'll raise the issue upstream. It's
>> non-free, so not too high on my priority list (and not much I can do
>> on my own anyways...)
>
> Could you please open a RM bug against ftp-master? There is no need to
> keep this in unstable, right? It holds back libssl1.0.0.
> Alternatively I could do it for you once I sorted most of the few other
> packages that hold on to libssl1.0.0 as well…
>
>> Thanks, everyone.
>> ~Scott
>
> Sebastian

Yes, I'll file a RM request. Upstream got back to me, they're working
on it - but no need to hold up ssl for now.
~Scott

Processed: Re: Bug#823880: libsvm : binary files in source package

[Debian Bug Tracking System]

Processing control commands:

> severity -1 minor
Bug #823880 [libsvm] libsvm : binary files in source package
Severity set to 'minor' from 'serious'

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

Bug#823880: libsvm : binary files in source package

[Christian Kastner]

Control: severity -1 minor

Hi Dominique,

On 2016-05-10 01:52, Dominique Belhachemi wrote:
> Package: libsvm
> Version: 3.12-1.1
> Severity: serious
>
> The source package contains binary files, see
> 
> https://sources.debian.net/src/libsvm/3.12-1.1/windows/
> https://sources.debian.net/src/libsvm/3.12-1.1/java/

I think there is a misunderstanding here: binaries per se are not a
violation of the Policy (which would indeed warrant a "serious"
severity). They are only a violation when the source is not provided.

See eg the following lintian tags with severity of just "pedantic":
  * source-contains-prebuilt-windows-binary
  * source-contains-prebuilt-java-object

In this particular case, the files in windows/ and java/ are just
pre-built binaries provided by upstream as a convenience to the user.
They are built from the very same source (see eg: Makefile.win).

Of course, it would better to repack and not include these at all, but
this is a minor issue.

> v3.12 is from 2012, please consider an update to a recent version (
> https://github.com/cjlin1/libsvm/releases )

Chen-Tse and I are already working on this.

Regards,
Christian




signature.asc
Description: OpenPGP digital signature

Bug#820312: marked as done (python-enum34: should conflict/replace python-enum)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 19:22:17 +
with message-id 
and subject line Bug#820312: fixed in enum34 1.1.5-1
has caused the Debian Bug report #820312,
regarding python-enum34: should conflict/replace python-enum
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.)


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

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'jessie'.
It installed fine in 'jessie', then the upgrade to 'stretch' fails.

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

2m17.8s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpRqftPg', 
'apt-get', '-y', 'install', 'python-laditools']
2m18.1s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
   python-laditools : Depends: python-enum34 but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.
2m18.1s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpRqftPg', 'apt-get', '-y', 'install', 'python-laditools']

the apt problemresolver reports:

  Investigating (0) python-enum [ amd64 ] < 0.4.4-3 > ( python )
  Broken python-enum:amd64 Conflicts on python-enum34 [ amd64 ] < none -> 
1.1.2-1 > ( python )
Considering python-enum34:amd64 -1 as a solution to python-enum:amd64 0
Added python-enum34:amd64 to the remove list
Fixing python-enum:amd64 via keep of python-enum34:amd64
  Investigating (1) python-laditools [ amd64 ] < 1.0.1-2 -> 1.1.0-2 > ( python )
  Broken python-laditools:amd64 Depends on python-enum34 [ amd64 ] < none -> 
1.1.2-1 > ( python )
Considering python-enum34:amd64 -1 as a solution to python-laditools:amd64 
1
Re-Instated python-enum34:amd64
  Investigating (1) python-enum [ amd64 ] < 0.4.4-3 > ( python )
  Broken python-enum:amd64 Conflicts on python-enum34 [ amd64 ] < none -> 
1.1.2-1 > ( python )
Considering python-enum34:amd64 -1 as a solution to python-enum:amd64 0
Added python-enum34:amd64 to the remove list
Fixing python-enum:amd64 via keep of python-enum34:amd64
  Investigating (2) python-laditools [ amd64 ] < 1.0.1-2 -> 1.1.0-2 > ( python )
  Broken python-laditools:amd64 Depends on python-enum34 [ amd64 ] < none -> 
1.1.2-1 > ( python )
Considering python-enum34:amd64 -1 as a solution to python-laditools:amd64 
1
  Done

Maybe it's sufficient to add a 
  Conflicts: python-enum
to python-laditools, but I haven't tested this.

cheers,

Andreas


python-laditools_1.1.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: enum34
Source-Version: 1.1.5-1

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

Debian distribution maintenance software
pp.
Barry Warsaw  (supplier of updated enum34 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: Wed, 11 May 2016 14:39:45 -0400
Source: enum34
Binary: python-enum34-doc python-enum34 pypy-enum34
Architecture: source all
Version: 1.1.5-1
Distribution: unstable
Urgency: medium
Maintainer: Barry Warsaw 
Changed-By: Barry Warsaw 
Description:
 pypy-enum34 - backport of Python 3.4's enum package (PyPy package)
 python-enum34 - backport of Python 3.4's enum package
 python-enum34-doc - backport of Python 3.4's enum package (documentation)
Closes: 793506 820312
Changes:
 enum34 (1.1.5-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
 

Bug#824039: marked as done (fontforge: symbol lookup error:)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 21:13:33 +0200
with message-id <1462994013.20054.0.ca...@debian.org>
and subject line Re: [Pkg-fonts-devel] Bug#824039: fontforge: symbol lookup 
error:
has caused the Debian Bug report #824039,
regarding fontforge: symbol lookup 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.)


-- 
824039: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontforge
Version: 20120731.b-7.1+b1
Severity: grave

I'm unable to run the program:

fontforge: symbol lookup error: /usr/lib/libgutils.so.1: undefined symbol: 
png_longjmp

Best regards

Janusz

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

Kernel: Linux 4.1.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 fontforge depends on:
ii  fontforge-common 20120731.b-7.1
ii  libc62.22-7
ii  libcairo21.14.6-1
ii  libfontconfig1   2.11.0-6.4
ii  libfontforge120120731.b-7.1+b1
ii  libfreetype6 2.6.3-3
ii  libgdraw420120731.b-7.1+b1
ii  libgif7  5.1.4-0.1
ii  libglib2.0-0 2.48.0-1
ii  libice6  2:1.0.9-1+b1
ii  libjpeg62-turbo  1:1.4.2-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpangoft2-1.0-01.40.1-1
ii  libpangoxft-1.0-01.40.1-1
ii  libpython2.7 2.7.11-8
ii  libsm6   2:1.2.2-1+b1
ii  libspiro01:0.5.20150702-4
ii  libtiff5 4.0.6-1
ii  libuninameslist0 0.5.20150701-1
ii  libx11-6 2:1.6.3-1
ii  libxft2  2.3.2-1
ii  libxml2  2.9.3+dfsg1-1

fontforge recommends no packages.

Versions of packages fontforge suggests:
pn  autotrace 
pn  fontforge-doc 
ii  fontforge-extras  0.3-4
pn  potrace   
pn  python-fontforge  

-- no debconf information

-- 
   ,   
Prof. dr hab. Janusz S. Bien -  Uniwersytet Warszawski (Katedra Lingwistyki 
Formalnej)
Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department)
jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/
--- End Message ---
--- Begin Message ---
Version: 20120731.b-7.2

Am Mittwoch, den 11.05.2016, 17:45 +0200 schrieb Janusz S. Bień:
> fontforge: symbol lookup error: /usr/lib/libgutils.so.1: undefined
> symbol: png_longjmp

This was the reason for the 20120731.b-7.2 upload, please upgrade your
packages.

Thanks,

Fabian


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

Processed: Re: FTBFS: test-suite fails on various architectures in testCallbackTransferFull

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #803415 [src:gjs] FTBFS: test-suite fails on various architectures in 
testCallbackTransferFull
Severity set to 'important' from 'serious'

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

Bug#803415: FTBFS: test-suite fails on various architectures in testCallbackTransferFull

[Michael Biebl]

Control: severity -1 important

I've decided to make the test-suite failures non-fatal again, as gjs was
blocking important updates in other packages from reaching testing.
Thus downgrading the severity.

We currently also have another, gobject-introspection 1.48 related,
regression in gjs:

https://bugzilla.gnome.org/show_bug.cgi?id=765465

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



signature.asc
Description: OpenPGP digital signature

Bug#824059: plasma-desktop: When used with pulseaudio, can make people deaf

[Sami Erjomaa]

I remember having similar problem with kde4 knotify
https://bugs.kde.org/show_bug.cgi?id=324975 and
https://bugs.kde.org/show_bug.cgi?id=345651. I can still partly reproduce
this with KF5 and gstreamer backend by playing notification and adjusting
the notification volume to 100%. After this the master volume is raised to
100% but all the other streams are lowered to keep the same voume level.

Since this is probably a very complicated issue that might be caused by
> pulseaudio,
> phonon, vlc as phonon backend or kdelibs, and it will probably take many
> years to be
> fixed, I suggest to ship plasma with a sane default and disable all audio
> notifications by default.
>

The second upstream bug says that gstreamer backend should manage the
volumes better. Could you try that?

Bug#820312: marked as pending

[Barry Warsaw]

tag 820312 pending
thanks

Hello,

Bug #820312 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=python-modules/packages/enum34.git;a=commitdiff;h=d0dc602

---
commit d0dc602f58cb2e04a0b559e79285e646d4bc2f26
Author: Barry Warsaw 
Date:   Wed May 11 14:39:40 2016 -0400

New upstream release.

* New upstream release.
  - Closes: #793506
  - Closes: #820312

diff --git a/debian/changelog b/debian/changelog
index db49fb4..f84459b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -4,7 +4,9 @@ enum34 (1.1.5-1) UNRELEASED; urgency=medium
   * Fixed VCS URL (https)
 
   [ Barry Warsaw ]
-  * New upstream release. (Closes: #793506)
+  * New upstream release.
+- Closes: #793506
+- Closes: #820312
   * d/control:
 - Bump Standards-Version to 3.9.8 with no other changes needed.
 - Swap Maintainer and Uploaders.

Bug#824047: marked as done (php-codecoverage: FTBFS: PHP_CodeCoverage_Report_HTMLTest::testForBankAccountTest BankAccount.php.html not match)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 18:44:46 +
with message-id 
and subject line Bug#824047: fixed in php-codecoverage 3.3.1+dfsg-2
has caused the Debian Bug report #824047,
regarding php-codecoverage: FTBFS: 
PHP_CodeCoverage_Report_HTMLTest::testForBankAccountTest   BankAccount.php.html 
not match
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.)


-- 
824047: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-codecoverage
Version: 3.3.1+dfsg-1
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,

php-codecoverage fails to build from source in unstable/amd64:

  [..]

  Creating config file /etc/php/7.0/mods-available/exif.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/fileinfo.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/ftp.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/gettext.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/iconv.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/pdo.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/phar.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/posix.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/shmop.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/sockets.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/sysvmsg.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/sysvsem.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/sysvshm.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/tokenizer.ini with new 
version
  Setting up libedit2:amd64 (3.1-20150325-1+b1) ...
  Setting up php7.0-phpdbg (7.0.6-3) ...
  update-alternatives: using /usr/bin/phpdbg7.0 to provide /usr/bin/phpdbg 
(phpdbg) in auto mode
  
  Creating config file /etc/php/7.0/phpdbg/php.ini with new version
  Setting up php7.0-json (7.0.6-3) ...
  
  Creating config file /etc/php/7.0/mods-available/json.ini with new version
  Setting up php7.0-opcache (7.0.6-3) ...
  
  Creating config file /etc/php/7.0/mods-available/opcache.ini with new version
  Setting up php7.0-readline (7.0.6-3) ...
  
  Creating config file /etc/php/7.0/mods-available/readline.ini with new version
  Setting up php7.0-cli (7.0.6-3) ...
  update-alternatives: using /usr/bin/php7.0 to provide /usr/bin/php (php) in 
auto mode
  update-alternatives: using /usr/bin/phar7.0 to provide /usr/bin/phar (phar) 
in auto mode
  update-alternatives: using /usr/bin/phar.phar7.0 to provide 
/usr/bin/phar.phar (phar.phar) in auto mode
  
  Creating config file /etc/php/7.0/cli/php.ini with new version
  Setting up php-xdebug (2.4.0-5) ...
  Setting up php-zeta-base (1.9-3) ...
  Setting up php-zeta-console-tools (1.7-3) ...
  Setting up php-cli (1:7.0+40) ...
  Setting up php-directory-scanner (1.3.1-3) ...
  Setting up phpab (1.21.0-2) ...
  Setting up php-symfony-yaml (2.8.4+dfsg-1) ...
  Setting up phpunit-recursion-context (1.0.2-2) ...
  Setting up phpunit-exporter (1.2.1-2) ...
  Setting up php-file-iterator (1.4.1-2) ...
  Setting up php-text-template (1.2.1-2) ...
  Setting up phpunit-code-unit-reverse-lookup (1.0.0-2) ...
  Setting up phpunit-environment (1.3.6-1) ...
  Setting up phpunit-version (2.0.0-2) ...
  Setting up php-codecoverage (3.3.1+dfsg-1) ...
  Setting up php-timer (1.0.7-2) ...
  Setting up php-doctrine-instantiator (1.0.5-2) ...
  Setting up phpunit-mock-object (3.1.3-1) ...
  Setting up php-phpdocumentor-reflection-docblock (2.0.4-2) ...
  Setting up phpunit-diff (1.4.1-2) ...
  Setting up phpunit-comparator (1.2.0-2) ...
  Setting up php-phpspec-prophecy (1.6.0-2) ...
  Setting up phpunit-global-state (1.1.1-2) ...
  Setting up phpunit-object-enumerator (1.0.0-2) ...
  Setting up phpunit-resource-operations (1.0.0-2) ...
  Setting up php-deepcopy (1.5.1-1) ...
  Setting up libxslt1.1:amd64 (1.1.28-3) ...
  Setting up php7.0-xml (7.0.6-3) ...
  
  Creating config file /etc/php/7.0/mods-available/dom.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/simplexml.ini with new 
version
  
  Creating config file /etc/php/7.0/mods-available/wddx.ini with new version
  
  Creating config file 

Processed: Bug#820312 marked as pending

[Debian Bug Tracking System]

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

> tag 820312 pending
Bug #820312 [python-enum34] python-enum34: should conflict/replace python-enum
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#823916 closed by Stefano Rivera <stefa...@debian.org> (Bug#823916: fixed in pypy 5.1.1+dfsg-1)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #823916 {Done: Stefano Rivera } [src:pypy] pypy: FTBFS 
on s390x
'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 pypy/5.1.1+dfsg-1.

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

Bug#823916: closed by Stefano Rivera <stefa...@debian.org> (Bug#823916: fixed in pypy 5.1.1+dfsg-1)

[Stefano Rivera]

Control: reopen -1

Test building in the archive...

I'm working with upstream on this.

SR

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#824059: plasma-desktop: When used with pulseaudio, can make people deaf

[Salvo Tomaselli]

Package: plasma-desktop
Version: 4:5.5.4-1
Severity: grave
Tags: upstream

Dear Maintainer,

I am reporting this with an high severity, because this can cause hear loss.

On a default install of debian with kde (recommends enabled), when playing 
music,
when a KDE notification appears, the overall volume goes up to 100%, which can
cause hearing loss.

I have tried to replicate, pressing "test" in systemsettings, for the audio
output of the notifications, and the volume always goes to 100%, regardless of
the initial value.

Sometimes the volume of amarok remains unchanged, and sometimes it goes to 100%
as well.

Since this is probably a very complicated issue that might be caused by 
pulseaudio,
phonon, vlc as phonon backend or kdelibs, and it will probably take many years 
to be
fixed, I suggest to ship plasma with a sane default and disable all audio
notifications by default.

This is probably the best solution in the short term. And I don't think this can
wait, since blasting sound at 100% volume when my setting was 12% can be
dangerous.

I hope you will not ignore this.

Best

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

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

Versions of packages plasma-desktop depends on:
ii  breeze   4:5.4.3-1
ii  kactivities  5.16.0-1
ii  kde-cli-tools4:5.4.3-1
ii  kded55.16.0-1
ii  kio  5.16.0-1.1
ii  libc62.22-7
ii  libcanberra0 0.30-3
ii  libfontconfig1   2.11.0-6.4
ii  libgcc1  1:6.1.1-1
ii  libkf5activities55.16.0-1
ii  libkf5activitiesexperimentalstats1   4:5.4.3-1
ii  libkf5archive5   5.16.0-1
ii  libkf5auth5  5.16.0-1
ii  libkf5baloo5 5.16.0-1
ii  libkf5bookmarks5 5.16.0-1
ii  libkf5codecs55.16.0-1
ii  libkf5completion55.16.0-1
ii  libkf5configcore55.16.0-1
ii  libkf5configgui5 5.16.0-1
ii  libkf5configwidgets5 5.16.0-1
ii  libkf5coreaddons55.16.0-1
ii  libkf5dbusaddons55.16.0-1
ii  libkf5emoticons-bin  5.16.0-2
ii  libkf5emoticons5 5.16.0-2
ii  libkf5globalaccel5   5.16.0-1
ii  libkf5guiaddons5 5.16.0-1
ii  libkf5i18n5  5.16.0-1
ii  libkf5iconthemes55.16.0-1
ii  libkf5itemmodels55.16.0-1
ii  libkf5itemviews5 5.16.0-1
ii  libkf5jobwidgets55.16.0-1
ii  libkf5kcmutils5  5.16.0-1
ii  libkf5kdelibs4support5   5.16.0-1
ii  libkf5kiocore5   5.16.0-1.1
ii  libkf5kiofilewidgets55.16.0-1.1
ii  libkf5kiowidgets55.16.0-1.1
ii  libkf5newstuff5  5.16.0-1
ii  libkf5notifications5 5.16.0-1
ii  libkf5notifyconfig5  5.16.0-1
ii  libkf5parts5 5.16.0-1
ii  libkf5people55.16.0-1
ii  libkf5peoplewidgets5 5.16.0-1
ii  libkf5plasma55.16.0-1
ii  libkf5plasmaquick5   5.16.0-1
ii  libkf5quickaddons5   5.16.0-1
ii  libkf5runner55.16.0-1
ii  libkf5service-bin5.16.0-1
ii  libkf5service5   5.16.0-1
ii  libkf5solid5 5.16.0-1
ii  libkf5sonnetui5  5.16.0-1
ii  libkf5wallet-bin 5.16.0-1
ii  libkf5wallet55.16.0-1
ii  libkf5widgetsaddons5 5.16.0-1
ii  libkf5windowsystem5  5.16.0-1
ii  libkf5xmlgui55.16.0-1
ii  libkfontinst54:5.4.3-1
ii  libkfontinstui5  4:5.4.3-1
ii  libkworkspace5-5 4:5.4.3-2
ii  libphonon4qt5-4  4:4.8.3-2
ii  libpulse-mainloop-glib0  8.0-2+b2
ii  libpulse08.0-2+b2
ii  libqt5concurrent55.5.1+dfsg-16+b1
ii  libqt5core5a 5.5.1+dfsg-16+b1
ii  libqt5dbus5   

Processed: limit source to php-codecoverage, tagging 824047

[Debian Bug Tracking System]

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

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

> tags 824047 + pending
Bug #824047 [src:php-codecoverage] php-codecoverage: FTBFS: 
PHP_CodeCoverage_Report_HTMLTest::testForBankAccountTest   BankAccount.php.html 
not match
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#824046: libtkx-perl: FTBFS: Tcl error 'Foo at /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking scalar result call

[gregor herrmann]

Control: tag -1 + confirmed

On Wed, 11 May 2016 17:34:56 +0100, Chris Lamb wrote:

> Source: libtkx-perl
> Version: 1.09-1
> Severity: serious
> Justification: fails to build from source

>   # Test 18 got: "Tcl error 'Foo at 
> /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking 
> scalar result call:\n\t\"error Foo\" at 
> /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 
> 588.\n\tTcl::call(Tcl=SCALAR(0x178d220), \"error\", \"Foo\") called at 
> /home/lamby/temp/cdt.20160511172312.jG2eA83qLd.libtkx-perl/libtkx-perl-1.09/blib/lib/Tkx.pm
>  line 329\n\teval {...} called at 
> /home/lamby/temp/cdt.20160511172312.jG2eA83qLd.libtkx-perl/libtkx-perl-1.09/blib/lib/Tkx.pm
>  line 329\n\tTkx::i::call(\"error\", \"Foo\") called at 
> /home/lamby/temp/cdt.20160511172312.jG2eA83qLd.libtkx-perl/libtkx-perl-1.09/blib/lib/Tkx.pm
>  line 51\n\tTkx::AUTOLOAD(\"Foo\") called at t/tcl.t line 38\n\teval {...} 
> called at t/tcl.t line 38\n" (t/tcl.t at line 39)
>   #Expected: "Foo at t/tcl.t line 38.\n"
>   #  t/tcl.t line 39 is: ok($@, "Foo at @{[__FILE__]} line @{[__LINE__ - 
> 1]}.\n");
>   t/tcl.t ... 
>   1..18
>   # Running under perl version 5.022002 for linux
>   # Current time local: Wed May 11 17:23:44 2016
>   # Current time GMT:   Wed May 11 16:23:44 2016
>   # Using Test.pm version 1.26
>   ok 1
>   ok 2
>   ok 3
>   ok 4
>   ok 5
>   ok 6
>   ok 7
>   ok 8
>   ok 9
>   ok 10
>   ok 11
>   ok 12
>   ok 13
>   ok 14
>   ok 15
>   ok 16
>   ok 17
>   not ok 18
>   Failed 1/18 subtests 
>   (in cleanup) Can't call method "DeleteCommand" on an undefined value at 
> /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 655 during global 
> destruction.

This seems to be caused by a recent change in libtcl-perl, which grew
a Tcl::Code::DESTROY method; it looks like the error doesn't refer to
the calling script (t/tcl.t) any more but to the module.

Not sure if we should just relax the test or if there's something to
be done in Tcl (all those warnings about DeleteCommand, also in the
same new method, don't like good either).


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Processed: your mail

[Debian Bug Tracking System]

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

> unblock 822318 by 754713
Bug #822318 [ftp.debian.org] RM: libpng -- RoQA; superseded by libpng1.6
822318 was blocked by: 821875 821765 822085 798167 822243 816101 822169 821797 
821799 821804 822731 823379 822237 821773 821798 801602 822687 822630 817938 
821766 821874 754713 822255 821215 822080 821800 818072
822318 was not blocking any bugs.
Removed blocking bug(s) of 822318: 754713
> --
Stopping processing here.

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

Processed: Re: Bug#824046: libtkx-perl: FTBFS: Tcl error 'Foo at /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking scalar result call

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + confirmed
Bug #824046 [src:libtkx-perl] libtkx-perl: FTBFS: Tcl error 'Foo at 
/usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking scalar 
result call
Added tag(s) confirmed.

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

Bug#824047: php-codecoverage: FTBFS: PHP_CodeCoverage_Report_HTMLTest::testForBankAccountTest BankAccount.php.html not match

[Chris Lamb]

Source: php-codecoverage
Version: 3.3.1+dfsg-1
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,

php-codecoverage fails to build from source in unstable/amd64:

  [..]

  Creating config file /etc/php/7.0/mods-available/exif.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/fileinfo.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/ftp.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/gettext.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/iconv.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/pdo.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/phar.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/posix.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/shmop.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/sockets.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/sysvmsg.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/sysvsem.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/sysvshm.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/tokenizer.ini with new 
version
  Setting up libedit2:amd64 (3.1-20150325-1+b1) ...
  Setting up php7.0-phpdbg (7.0.6-3) ...
  update-alternatives: using /usr/bin/phpdbg7.0 to provide /usr/bin/phpdbg 
(phpdbg) in auto mode
  
  Creating config file /etc/php/7.0/phpdbg/php.ini with new version
  Setting up php7.0-json (7.0.6-3) ...
  
  Creating config file /etc/php/7.0/mods-available/json.ini with new version
  Setting up php7.0-opcache (7.0.6-3) ...
  
  Creating config file /etc/php/7.0/mods-available/opcache.ini with new version
  Setting up php7.0-readline (7.0.6-3) ...
  
  Creating config file /etc/php/7.0/mods-available/readline.ini with new version
  Setting up php7.0-cli (7.0.6-3) ...
  update-alternatives: using /usr/bin/php7.0 to provide /usr/bin/php (php) in 
auto mode
  update-alternatives: using /usr/bin/phar7.0 to provide /usr/bin/phar (phar) 
in auto mode
  update-alternatives: using /usr/bin/phar.phar7.0 to provide 
/usr/bin/phar.phar (phar.phar) in auto mode
  
  Creating config file /etc/php/7.0/cli/php.ini with new version
  Setting up php-xdebug (2.4.0-5) ...
  Setting up php-zeta-base (1.9-3) ...
  Setting up php-zeta-console-tools (1.7-3) ...
  Setting up php-cli (1:7.0+40) ...
  Setting up php-directory-scanner (1.3.1-3) ...
  Setting up phpab (1.21.0-2) ...
  Setting up php-symfony-yaml (2.8.4+dfsg-1) ...
  Setting up phpunit-recursion-context (1.0.2-2) ...
  Setting up phpunit-exporter (1.2.1-2) ...
  Setting up php-file-iterator (1.4.1-2) ...
  Setting up php-text-template (1.2.1-2) ...
  Setting up phpunit-code-unit-reverse-lookup (1.0.0-2) ...
  Setting up phpunit-environment (1.3.6-1) ...
  Setting up phpunit-version (2.0.0-2) ...
  Setting up php-codecoverage (3.3.1+dfsg-1) ...
  Setting up php-timer (1.0.7-2) ...
  Setting up php-doctrine-instantiator (1.0.5-2) ...
  Setting up phpunit-mock-object (3.1.3-1) ...
  Setting up php-phpdocumentor-reflection-docblock (2.0.4-2) ...
  Setting up phpunit-diff (1.4.1-2) ...
  Setting up phpunit-comparator (1.2.0-2) ...
  Setting up php-phpspec-prophecy (1.6.0-2) ...
  Setting up phpunit-global-state (1.1.1-2) ...
  Setting up phpunit-object-enumerator (1.0.0-2) ...
  Setting up phpunit-resource-operations (1.0.0-2) ...
  Setting up php-deepcopy (1.5.1-1) ...
  Setting up libxslt1.1:amd64 (1.1.28-3) ...
  Setting up php7.0-xml (7.0.6-3) ...
  
  Creating config file /etc/php/7.0/mods-available/dom.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/simplexml.ini with new 
version
  
  Creating config file /etc/php/7.0/mods-available/wddx.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/xml.ini with new version
  
  Creating config file /etc/php/7.0/mods-available/xmlreader.ini with new 
version
  
  Creating config file /etc/php/7.0/mods-available/xmlwriter.ini with new 
version
  
  Creating config file /etc/php/7.0/mods-available/xsl.ini with new version
  Setting up php-xml (1:7.0+40) ...
  Setting up phpunit (5.3.2+dfsg-1) ...
  Setting up php-pear (1:1.10.1+submodules+notgz-8) ...
  Setting up pkg-php-tools (1.34) ...
  Setting up php-codecoverage-build-deps (3.3.1+dfsg-1) ...
  Processing triggers for libc-bin (2.22-7) ...
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package php-codecoverage
  dpkg-buildpackage: info: source version 3.3.1+dfsg-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by David Prvot 
   dpkg-source --before-build php-codecoverage-3.3.1+dfsg
  

Bug#824046: libtkx-perl: FTBFS: Tcl error 'Foo at /usr/lib/x86_64-linux-gnu/perl5/5.22/Tcl.pm line 585.\n' while invoking scalar result call

[Chris Lamb]

Source: libtkx-perl
Version: 1.09-1
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,

libtkx-perl fails to build from source in unstable/amd64:

  [..]

  Preparing to unpack .../libglapi-mesa_11.2.1-2_amd64.deb ...
  Unpacking libglapi-mesa:amd64 (11.2.1-2) ...
  Selecting previously unselected package libx11-xcb1:amd64.
  Preparing to unpack .../libx11-xcb1_2%3a1.6.3-1_amd64.deb ...
  Unpacking libx11-xcb1:amd64 (2:1.6.3-1) ...
  Selecting previously unselected package libxcb-dri2-0:amd64.
  Preparing to unpack .../libxcb-dri2-0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-dri2-0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-dri3-0:amd64.
  Preparing to unpack .../libxcb-dri3-0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-dri3-0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-glx0:amd64.
  Preparing to unpack .../libxcb-glx0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-glx0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-present0:amd64.
  Preparing to unpack .../libxcb-present0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-present0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-randr0:amd64.
  Preparing to unpack .../libxcb-randr0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-randr0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-render0:amd64.
  Preparing to unpack .../libxcb-render0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-render0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-shape0:amd64.
  Preparing to unpack .../libxcb-shape0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-shape0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-sync1:amd64.
  Preparing to unpack .../libxcb-sync1_1.11.1-1_amd64.deb ...
  Unpacking libxcb-sync1:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxcb-xfixes0:amd64.
  Preparing to unpack .../libxcb-xfixes0_1.11.1-1_amd64.deb ...
  Unpacking libxcb-xfixes0:amd64 (1.11.1-1) ...
  Selecting previously unselected package libxfixes3:amd64.
  Preparing to unpack .../libxfixes3_1%3a5.0.1-2+b2_amd64.deb ...
  Unpacking libxfixes3:amd64 (1:5.0.1-2+b2) ...
  Selecting previously unselected package libxdamage1:amd64.
  Preparing to unpack .../libxdamage1_1%3a1.1.4-2+b1_amd64.deb ...
  Unpacking libxdamage1:amd64 (1:1.1.4-2+b1) ...
  Selecting previously unselected package libxshmfence1:amd64.
  Preparing to unpack .../libxshmfence1_1.2-1_amd64.deb ...
  Unpacking libxshmfence1:amd64 (1.2-1) ...
  Selecting previously unselected package libxxf86vm1:amd64.
  Preparing to unpack .../libxxf86vm1_1%3a1.1.4-1_amd64.deb ...
  Unpacking libxxf86vm1:amd64 (1:1.1.4-1) ...
  Selecting previously unselected package libgl1-mesa-glx:amd64.
  Preparing to unpack .../libgl1-mesa-glx_11.2.1-2_amd64.deb ...
  Unpacking libgl1-mesa-glx:amd64 (11.2.1-2) ...
  Selecting previously unselected package libpixman-1-0:amd64.
  Preparing to unpack .../libpixman-1-0_0.33.6-1_amd64.deb ...
  Unpacking libpixman-1-0:amd64 (0.33.6-1) ...
  Selecting previously unselected package libfontenc1:amd64.
  Preparing to unpack .../libfontenc1_1%3a1.1.3-1_amd64.deb ...
  Unpacking libfontenc1:amd64 (1:1.1.3-1) ...
  Selecting previously unselected package libxfont1:amd64.
  Preparing to unpack .../libxfont1_1%3a1.5.1-1_amd64.deb ...
  Unpacking libxfont1:amd64 (1:1.5.1-1) ...
  Selecting previously unselected package xvfb.
  Preparing to unpack .../xvfb_2%3a1.18.3-1_amd64.deb ...
  Unpacking xvfb (2:1.18.3-1) ...
  Processing triggers for libc-bin (2.22-7) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for systemd (229-5) ...
  Setting up libtcl8.6:amd64 (8.6.5+dfsg-2) ...
  Setting up libtcl-perl (1.04+ds-1) ...
  Setting up libpng16-16:amd64 (1.6.21-4) ...
  Setting up libfreetype6:amd64 (2.6.3-3+b1) ...
  Setting up ucf (3.0036) ...
  Setting up fonts-dejavu-core (2.35-1) ...
  Setting up fontconfig-config (2.11.0-6.4) ...
  Setting up libfontconfig1:amd64 (2.11.0-6.4) ...
  Setting up libxau6:amd64 (1:1.0.8-1) ...
  Setting up libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Setting up libxcb1:amd64 (1.11.1-1) ...
  Setting up libx11-data (2:1.6.3-1) ...
  Setting up libx11-6:amd64 (2:1.6.3-1) ...
  Setting up libxext6:amd64 (2:1.3.3-1) ...
  Setting up libxrender1:amd64 (1:0.9.9-2) ...
  Setting up libxft2:amd64 (2.3.2-1) ...
  Setting up x11-common (1:7.7+15) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  Setting up libxss1:amd64 (1:1.2.2-1) ...
  Setting up libtk8.6:amd64 (8.6.5-1) ...
  Setting up tk8.6 (8.6.5-1) ...
  Setting up tcl8.6 (8.6.5+dfsg-2) ...
  Setting up tcl (8.6.0+9) ...
  Setting up tk (8.6.0+9) ...
  Setting up 

Bug#824048: python-biopython: FTBFS: AssertionError: 10 != 1

[Chris Lamb]

Source: python-biopython
Version: 1.66+dfsg-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,

python-biopython fails to build from source in unstable/amd64:

  [..]

   cp -a Doc/Tutorial.tex 
/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/Doc;
 \
   cp -a Doc/Tutorial 
/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/Doc;
 \
   cp -a Doc/examples 
/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/Doc;
 \
   cp -a Tests 
/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build;
 \
   cd 
/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/Tests;
 \
   env DIALIGN2_DIR=/usr/share/dialign 
EMBOSS_ROOT=/usr/lib/emboss 
HOME=/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/home
 python2.7 run_tests.py --offline
  test_Ace ... ok
  test_AlignIO ... ok
  test_AlignIO_ClustalIO ... ok
  test_AlignIO_EmbossIO ... ok
  test_AlignIO_FastaIO ... ok
  test_AlignIO_PhylipIO ... ok
  test_AlignIO_convert ... ok
  test_Application ... ok
  test_BWA_tool ... ok
  test_BioSQL_mysql_connector ... skipping. Install mysql.connector if you want 
to use mysql with BioSQL 
  test_BioSQL_sqlite3 ... ok
  test_CAPS ... ok
  test_CelFile ... ok
  test_Chi2 ... ok
  test_ClustalOmega_tool ... ok
  test_Clustalw_tool ... ok
  test_Cluster ... ok
  test_CodonTable ... ok
  test_CodonUsage ... ok
  test_ColorSpiral ... ok
  test_Compass ... ok
  test_Consensus ... ok
  test_Crystal ... ok
  test_DSSP_tool ... ok
  test_Dialign_tool ... ok
  test_DocSQL ... ok
  test_EMBL_unittest ... ok
  test_Emboss ... ok
  test_EmbossPrimer ... ok
  test_Entrez ... ok
  test_Entrez_online ... skipping. internet not available
  test_Enzyme ... ok
  test_FSSP ... ok
  test_Fasttree_tool ... ok
  test_File ... ok
  test_GACrossover ... ok
  test_GAMutation ... ok
  test_GAOrganism ... ok
  test_GAQueens ... ok
  test_GARepair ... ok
  test_GASelection ... ok
  test_GenBank ... ok
  test_GenBank_unittest ... ok
  test_GenomeDiagram ... ok
  test_GraphicsBitmaps ... ok
  test_GraphicsChromosome ... ok
  test_GraphicsDistribution ... ok
  test_GraphicsGeneral ... ok
  test_HMMCasino ... ok
  test_HMMGeneral ... ok
  test_KDTree ... ok
  test_KEGG ... ok
  test_KEGG_online ... skipping. internet not available
  test_KGML_graphics ... ok
  test_KGML_graphics_online ... skipping. internet not available
  test_KGML_nographics ... ok
  test_KeyWList ... ok
  test_Location ... ok
  test_LogisticRegression ... ok
  test_MMCIF ... ok
  test_Mafft_tool ... ok
  test_MarkovModel ... ok
  test_Medline ... ok
  test_Motif ... ok
  test_Muscle_tool ... ok
  test_NCBITextParser ... ok
  test_NCBIXML ... ok
  test_NCBI_BLAST_tools ... 
/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/Tests/test_NCBI_BLAST_tools.py:280:
 UserWarning: NCBI BLAST+ deltablast and Biopython out sync. Please update 
Biopython, or report this issue if you are already using the latest version. 
(Extra args: ; Missing: -save_each_pssm,-save_pssm_after_last_round)
",".join(sorted(missing
  
/home/lamby/temp/cdt.20160511172943.3m3eRDBdi6.python-biopython/python-biopython-1.66+dfsg/.pybuild/pythonX.Y_2.7/build/Tests/test_NCBI_BLAST_tools.py:280:
 UserWarning: NCBI BLAST+ psiblast and Biopython out sync. Please update 
Biopython, or report this issue if you are already using the latest version. 
(Extra args: ; Missing: -save_each_pssm,-save_pssm_after_last_round)
",".join(sorted(missing
  FAIL
  test_NCBI_qblast ... skipping. internet not available
  test_NNExclusiveOr ... ok
  test_NNGene ... ok
  test_NNGeneral ... ok
  test_Nexus ... ok
  test_PAML_baseml ... ok
  test_PAML_codeml ... ok
  test_PAML_yn00 ... ok
  test_PDB ... ok
  test_PDB_KDTree ... ok
  test_ParserSupport ... ok
  test_Pathway ... ok
  test_Phd ... ok
  test_Phylo ... ok
  test_PhyloXML ... ok
  test_Phylo_CDAO ... ok
  test_Phylo_NeXML ... ok
  test_Phylo_depend ... 
/usr/lib/python2.7/dist-packages/matplotlib/font_manager.py:273: UserWarning: 
Matplotlib is building the font cache using fc-list. This may take a moment.
warnings.warn('Matplotlib is building the font cache using fc-list. This 
may take a moment.')
  ok
  test_PopGen_FDist_nodepend ... ok
  test_PopGen_FastSimCoal ... skipping. Install fastsimcoal 

Bug#824045: groovycsv: FTBFS: No cached version of org.codehaus.groovy:groovy-all:1.7.3 available for offline mode.

[Chris Lamb]

Source: groovycsv
Version: 1.0-1
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,

groovycsv fails to build from source in unstable/amd64:

  [..]

  Adding debian:VeriSign_Universal_Root_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_1_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_2_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G2.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem
  Adding debian:Verisign_Class_3_Public_Primary_Certification_Authority_2.pem
  Adding debian:Visa_eCommerce_Root.pem
  Adding debian:WellsSecure_Public_Root_Certificate_Authority.pem
  Adding debian:WoSign.pem
  Adding debian:WoSign_China.pem
  Adding debian:XRamp_Global_CA_Root.pem
  Adding debian:certSIGN_ROOT_CA.pem
  Adding debian:ePKI_Root_Certification_Authority.pem
  Adding debian:thawte_Primary_Root_CA.pem
  Adding debian:thawte_Primary_Root_CA_-_G2.pem
  Adding debian:thawte_Primary_Root_CA_-_G3.pem
  done.
  done.
  Setting up openjdk-8-jre-headless:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmid to 
provide /usr/bin/rmid (rmid) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java to 
provide /usr/bin/java (java) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/keytool 
to provide /usr/bin/keytool (keytool) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/jjs to 
provide /usr/bin/jjs (jjs) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/pack200 
to provide /usr/bin/pack200 (pack200) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/rmiregistry to provide 
/usr/bin/rmiregistry (rmiregistry) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/unpack200 to provide 
/usr/bin/unpack200 (unpack200) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/orbd to 
provide /usr/bin/orbd (orbd) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/servertool to provide 
/usr/bin/servertool (servertool) in auto mode
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/tnameserv to provide 
/usr/bin/tnameserv (tnameserv) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/jexec to 
provide /usr/bin/jexec (jexec) in auto mode
  Setting up default-jre-headless (2:1.8-57) ...
  Setting up openjdk-8-jre:amd64 (8u91-b14-2) ...
  update-alternatives: using 
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/policytool to provide 
/usr/bin/policytool (policytool) in auto mode
  Setting up default-jre (2:1.8-57) ...
  Setting up openjdk-8-jdk-headless:amd64 (8u91-b14-2) ...
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/idlj to 
provide /usr/bin/idlj (idlj) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jdeps to 
provide /usr/bin/jdeps (jdeps) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/wsimport to 
provide /usr/bin/wsimport (wsimport) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/rmic to 
provide /usr/bin/rmic (rmic) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jinfo to 
provide /usr/bin/jinfo (jinfo) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jsadebugd to 
provide /usr/bin/jsadebugd (jsadebugd) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/native2ascii 
to provide /usr/bin/native2ascii (native2ascii) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstat to 
provide /usr/bin/jstat (jstat) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javadoc to 
provide /usr/bin/javadoc (javadoc) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javah to 
provide /usr/bin/javah (javah) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jstack to 
provide /usr/bin/jstack (jstack) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/jrunscript 
to provide /usr/bin/jrunscript (jrunscript) in auto mode
  update-alternatives: using /usr/lib/jvm/java-8-openjdk-amd64/bin/javac to 
provide /usr/bin/javac (javac) in auto 

Bug#821347: libsecret testsuite failures on mipsel

[Andreas Henriksson]

Hello Aurelien Jarno.

Thanks for so quickly and thoroughly investigating these issues!

On Wed, May 11, 2016 at 05:39:08PM +0200, Aurelien Jarno wrote:
[...]
> A workaround might be to always build libsecret on the octeon build
> daemons. Currently that means the package might stay much longer in
> the build queue before being built, but we should deploy more of such
> machines in the next weeks. Otherwise it needs a deeper investigation
> which will take more time, as one has to understand the code to be
> able to debug it.

I think taking the longer build times is something we can definitely
live with given the current circumstances, since it would ofcourse
be a big improvement over not getting the builds through at all!

Regards,
Andreas Henriksson

Bug#824039: fontforge: symbol lookup error:

[Janusz S. Bień]

Package: fontforge
Version: 20120731.b-7.1+b1
Severity: grave

I'm unable to run the program:

fontforge: symbol lookup error: /usr/lib/libgutils.so.1: undefined symbol: 
png_longjmp

Best regards

Janusz

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

Kernel: Linux 4.1.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 fontforge depends on:
ii  fontforge-common 20120731.b-7.1
ii  libc62.22-7
ii  libcairo21.14.6-1
ii  libfontconfig1   2.11.0-6.4
ii  libfontforge120120731.b-7.1+b1
ii  libfreetype6 2.6.3-3
ii  libgdraw420120731.b-7.1+b1
ii  libgif7  5.1.4-0.1
ii  libglib2.0-0 2.48.0-1
ii  libice6  2:1.0.9-1+b1
ii  libjpeg62-turbo  1:1.4.2-2
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpangoft2-1.0-01.40.1-1
ii  libpangoxft-1.0-01.40.1-1
ii  libpython2.7 2.7.11-8
ii  libsm6   2:1.2.2-1+b1
ii  libspiro01:0.5.20150702-4
ii  libtiff5 4.0.6-1
ii  libuninameslist0 0.5.20150701-1
ii  libx11-6 2:1.6.3-1
ii  libxft2  2.3.2-1
ii  libxml2  2.9.3+dfsg1-1

fontforge recommends no packages.

Versions of packages fontforge suggests:
pn  autotrace 
pn  fontforge-doc 
ii  fontforge-extras  0.3-4
pn  potrace   
pn  python-fontforge  

-- no debconf information

-- 
   ,   
Prof. dr hab. Janusz S. Bien -  Uniwersytet Warszawski (Katedra Lingwistyki 
Formalnej)
Prof. Janusz S. Bien - University of Warsaw (Formal Linguistics Department)
jsb...@uw.edu.pl, jsb...@mimuw.edu.pl, http://fleksem.klf.uw.edu.pl/~jsbien/

Bug#821347: libsecret testsuite failures on mipsel

[Aurelien Jarno]

On 2016-05-10 18:02, Andreas Henriksson wrote:
> Hello mipsel porters!

Hi,

> The libsecret package currently suffers from FTBFS on mipsel
> because of two testsuite failures and your help fixing these
> would be much appreciated so we can move on elsewhere.
> 
> The problem is tracked in debian bug #821347 (CCed).
> 
> >From 
> >https://buildd.debian.org/status/fetch.php?pkg=libsecret=mipsel=0.18.5-1=1461171471
> > :
> 
> FAIL: test-session 4 /session/ensure-async-aes

This test is fully reproducible on Loongson 3 machines (almost all our
mips*el build daemons, and the porterbox), but I have not been able to
reproduce it on an Octeon machine, nor on a CI20 board nor under QEMU. I
therefore believe there is a bug specific to the Loongson 3 there.
Compared to the other machines they have 16kB pages (instead of 4kB), I
don't know if it could be the issue as I haven't investigated more yet.

> FAIL: test-collection 18 /collection/delete-sync

This one fail intermittently only, though again I have only seen it
failing on Loongson 3 machines. It looks like tests are done using a
random seed, so the result might depends on that.
 
> Please note that the second failure also happens on s390x.
> I've only contacted you in hope that your fixes might positively
> effect the s390x build, but you might want to contact and join
> forces with the s390x porters.

This looks like a different issue, as it doesn't fail on s390x, but
instead hangs, and in addition this is fully reproducible not
intermittent.

A workaround might be to always build libsecret on the octeon build
daemons. Currently that means the package might stay much longer in
the build queue before being built, but we should deploy more of such
machines in the next weeks. Otherwise it needs a deeper investigation
which will take more time, as one has to understand the code to be
able to debug it.

Aurelien

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

Processed: found 823510 in 2.4.0-1

[Debian Bug Tracking System]

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

> found 823510 2.4.0-1
Bug #823510 [php-react-promise] Useless in Debian
Marked as found in versions php-react-promise/2.4.0-1.
> thanks
Stopping processing here.

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

Bug#821484: freedombox-setup: PHP 7.0 Transition

[Sunil Mohan Adapa]

Attached is patch I prepared as discussed.  This patch to the postinst
script will disable php5 and enable php7.0 module.  This rule is applied
when upgrading from version less than or equal to 0.9.  It is not
applied when doing a fresh install.

I believe that after applying this patch, we need to make a new release
0.9.1 to fix the php migration issue.

I have tested as follows: I have taken a fresh 0.7.2 image and upgraded
to latest sid.  I can see that php7 is not installed.  Then after
installing the deb package with this patch included, php7 got installed
and freedombox has successfully switch the enabled version of php to
php7.  I have tested shaarli, tt-rss (reported #824029), roundcube
(needs update to 1.2beta for php7 support).

-- 
Sunil
From 619a2c55e56a65b87e9f006cc7e3385e52d0d3c3 Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa 
Date: Wed, 11 May 2016 14:14:45 +0530
Subject: [PATCH] When upgrading from < 0.9 enable php7

When upgrading from a version less then 0.9 and if php5 is enabled (not
disabled by user for any reason) then disable php5 and enable php7.0
module (php7.0 conflicts with php5).

Hack around the problem that apache maintainer scripts don't allow
disabling a module during postinst configure phase.
---
 debian/freedombox-setup.postinst | 19 +++
 1 file changed, 19 insertions(+)

diff --git a/debian/freedombox-setup.postinst b/debian/freedombox-setup.postinst
index 5351b6e..533824d 100644
--- a/debian/freedombox-setup.postinst
+++ b/debian/freedombox-setup.postinst
@@ -20,6 +20,25 @@ if dpkg --compare-versions "$2" le "0.0.23" &&
 rmdir /var/freedombox
 fi
 
+# Enable php7.0 Apache module when upgrading from olders version to
+# 0.9.1 or above
+if [ -e /usr/share/apache2/apache2-maintscript-helper ] ; then
+. /usr/share/apache2/apache2-maintscript-helper
+
+if dpkg --compare-versions "$2" le-nl "0.9" ; then
+if apache2_has_module php5 ; then
+# XXX: Hack around maintainer script refusing to disable a
+# module during configure
+method="$APACHE2_MAINTSCRIPT_METHOD"
+APACHE2_MAINTSCRIPT_METHOD="remove"
+apache2_invoke dismod php5
+APACHE2_MAINTSCRIPT_METHOD="$method"
+
+apache2_invoke enmod php7.0
+fi
+fi
+fi
+
 # Setup motd
 if [ "$1" = "configure" ] && [ -f /etc/motd ] && [ ! -L /etc/motd ] ; then
 mkdir -p /etc/update-motd.d
-- 
2.8.1



signature.asc
Description: OpenPGP digital signature

Processed: affects 823510

[Debian Bug Tracking System]

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

> affects 823510 2.4.0-1
Bug #823510 [php-react-promise] Useless in Debian
Added indication that 823510 affects 2.4.0-1
> thanks
Stopping processing here.

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

Processed: Re: codeblocks: Codeblocks crashes very frequently

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #820489 [codeblocks] codeblocks: Codeblocks crashes very frequently
Severity set to 'important' from 'grave'

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

Bug#820489: codeblocks: Codeblocks crashes very frequently

[Benedikt Wildenhain]

Package: codeblocks
Version: 13.12+dfsg-4
Tags: moreinfo
Control: severity -1 important

On Fri, Apr 08, 2016 at 09:20:19PM -0300, Alejandro Carrazzoni wrote:
> Codeblocks very frequently crashes suddenly with no error message when editing
> code, particularly when the code involves templates. I'm attaching the .xml
> crash log of the last crash.
I played arround a little bit using codeblocks, but couldn't cause it to
crash with a current unstable/sid Debian GNU/Linux on amd64. Does this
bug still occur with the current dependencies of the package?

If this is still the case, could you create a backtrace as described on
https://wiki.debian.org/HowToGetABacktrace?

Below are the dependencies installed on my system:

Versions of packages codeblocks depends on:
ii  codeblocks-common13.12+dfsg-4
ii  libatk1.0-0  2.20.0-1
ii  libc62.22-7
ii  libcairo21.14.6-1+b1
ii  libcodeblocks0   13.12+dfsg-4
ii  libfontconfig1   2.11.0-6.4
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.1.1-1
ii  libgdk-pixbuf2.0-0   2.34.0-1
ii  libglib2.0-0 2.48.0-1
ii  libgtk2.0-0  2.24.30-1.1
ii  libpango-1.0-0   1.40.1-1
ii  libpangocairo-1.0-0  1.40.1-1
ii  libpangoft2-1.0-01.40.1-1
ii  libstdc++6   6.1.1-1
ii  libwxbase3.0-0v5 3.0.2+dfsg-1.3+b1
ii  libwxgtk3.0-0v5  3.0.2+dfsg-1.3+b1

Versions of packages codeblocks recommends:
ii  g++4:5.3.1-1
ii  gcc4:5.3.1-1
ii  gdb-minimal [gdb]  7.10-1+b1
ii  xterm  324-1

Versions of packages codeblocks suggests:
pn  codeblocks-contrib  
pn  libwxgtk3.0-dev 

-- 
Benedikt Wildenhain, M.Sc., Wiss. Mitarbeiter - Hardwarenahe IT-Systeme
Hochschule Bochum - Bochum University of Applied Sciences
Campus Velbert/Heiligenhaus - http://www.hs-bochum.de/cvh/
Höseler Platz 2, Heiligenhaus, Raum 2.28, Tel +49 (0)2056 158744

Bug#823069: marked as done (live-boot-initramfs-tools: wrongly adds directories in /root to the PATH)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 13:51:28 +
with message-id <e1b0uxw-77...@franck.debian.org>
and subject line Bug#823069: fixed in live-boot 1:20160511
has caused the Debian Bug report #823069,
regarding live-boot-initramfs-tools: wrongly adds directories in /root to the 
PATH
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.)


-- 
823069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: live-boot-initramfs-tools
Version: 1:20151213
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?
 We tried to update the SolydXK EE (Enthusiast's Editions following Debian 
stretch) ISOs and found that the current update in busybox caused a kernel 
panic while booting live.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Update busybox (version 1:1.22.0-17 to  1:1.22.0-19), update live-boot and 
live-boot-initramfs-tools to the latest versions.

   * What was the outcome of this action?
 Kernel panic.
 
 This output is relevant:
 Running /scripts/init-bottom
 mount: /dev is write-protected, mounting read-only
 mount: /dev is not a block device

 The error is caused in /usr/share/initramfs-tools/scripts/init-bottom/udev
 Line: mount -n -o move /dev ${rootmnt}/dev

 This line is also present in Debian stable and does not cause a problem 
there.
 When we do not upgrade busybox we can successfully boot live.
 This problem does not occur when upgrading busybox on an installed system, 
only live.

   * What outcome did you expect instead?
 A bootable live session.

   > I can provide an ISO if you whish so.



-- System Information:
Distributor ID: SolydXK
Description:SolydK EE 9 64-bit
Release:stretch/sid
Codename:   solydxk
Architecture: x86_64

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

Versions of packages live-boot-initramfs-tools depends on:
pn  busybox | busybox-initramfs  1:1.22.0-19
ii  initramfs-tools  0.125
ii  udev 229-4

live-boot-initramfs-tools recommends no packages.

live-boot-initramfs-tools suggests no packages.
--- End Message ---
--- Begin Message ---
Source: live-boot
Source-Version: 1:20160511

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

Debian distribution maintenance software
pp.
Raphaël Hertzog <hert...@debian.org> (supplier of updated live-boot 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: Wed, 11 May 2016 11:40:37 +0200
Source: live-boot
Binary: live-boot live-boot-doc live-boot-initramfs-tools
Architecture: source
Version: 1:20160511
Distribution: unstable
Urgency: medium
Maintainer: Live Systems Maintainers <debian-l...@lists.debian.org>
Changed-By: Raphaël Hertzog <hert...@debian.org>
Description:
 live-boot  - Live System Boot Components
 live-boot-doc - Live System Boot Components (documentation)
 live-boot-initramfs-tools - Live System Boot Components (initramfs-tools 
backend)
Closes: 823069
Changes:
 live-boot (1:20160511) unstable; urgency=medium
 .
   * Team upload.
   * Update build system to rely on "dpkg-parsechangelog -S Version" instead
 of outdated VERSION file.
   * No longer modify PATH to point to /root and thus stop using executables
 from /root. Closes: #823069
   * Drop debian/source/local-options as the only option it contained was
 not applicable to 3.0 (native) source format.
   * Drop debian/source/options and dh_builddeb override as XZ compression is
 the default now.
Checksums-Sha1:
 d850509494ce58fb79ccbb1c902a97a2e55ffb88 1488 live-boot_20160511.dsc
 fa05090ff5449e5ace23fdf4750a01388e095824 99652 live-boot_20160511.tar.xz
Checksums-Sha256:
 ca52a13f86d57ec1f54ff47ff1578e8f3ee2aaa1f77e2ff02e902b75

Bug#708459: cairo-5c: FTBFS: make[3]: *** [check-TESTS] Error 1

[Fernando Seiti Furusato]

Source: cairo-5c
Followup-For: Bug #708459

user debian-powe...@lists.debian.org
usertags 708459 + ppc64el

thanks

This also affects ppc64el architecture.
I recently tried to build it and there are more tests failing.

The full log (although a little old) can be found at:
https://buildd.debian.org/status/fetch.php?pkg=cairo-5c=ppc64el=1.8.1=1410483854

Thanks.

Fernando

Bug#820866: marked as done (r-cran-tgp: FTBFS: cmath:171:3: error: template with C linkage)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 13:27:50 +
with message-id 
and subject line Bug#820866: fixed in r-cran-tgp 2.4-14-1
has caused the Debian Bug report #820866,
regarding r-cran-tgp: FTBFS: cmath:171:3: error: template with C linkage
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.)


-- 
820866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-tgp
Version: 2.4-9-1
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,

r-cran-tgp fails to build from source in unstable/amd64:

  [..]

  /usr/include/c++/5/cmath: At global scope:
  /usr/include/c++/5/cmath:171:3: error: template with C linkage
 template
 ^
  /usr/include/c++/5/cmath: In function 'long double std::ceil(long double)':
  /usr/include/c++/5/cmath:188:23: error: conflicting declaration of C function 
'long double std::ceil(long double)'
 ceil(long double __x)
 ^
  /usr/include/c++/5/cmath:184:3: note: previous declaration 'float 
std::ceil(float)'
 ceil(float __x)
 ^
  /usr/include/c++/5/cmath: At global scope:
  /usr/include/c++/5/cmath:192:3: error: template with C linkage
 template
 ^
  /usr/include/c++/5/cmath: In function 'long double std::cos(long double)':
  /usr/include/c++/5/cmath:207:22: error: conflicting declaration of C function 
'long double std::cos(long double)'
 cos(long double __x)
^
  /usr/include/c++/5/cmath:203:3: note: previous declaration 'float 
std::cos(float)'
 cos(float __x)
 ^
  /usr/include/c++/5/cmath: At global scope:
  /usr/include/c++/5/cmath:211:3: error: template with C linkage
 template
 ^
  /usr/include/c++/5/cmath: In function 'long double std::cosh(long double)':
  /usr/include/c++/5/cmath:226:23: error: conflicting declaration of C function 
'long double std::cosh(long double)'
 cosh(long double __x)
 ^
  /usr/include/c++/5/cmath:222:3: note: previous declaration 'float 
std::cosh(float)'
 cosh(float __x)
 ^
  /usr/include/c++/5/cmath: At global scope:
  /usr/include/c++/5/cmath:230:3: error: template with C linkage
 template
 ^
  /usr/include/c++/5/cmath: In function 'long double std::exp(long double)':
  /usr/include/c++/5/cmath:245:22: error: conflicting declaration of C function 
'long double std::exp(long double)'
 exp(long double __x)
^
  /usr/include/c++/5/cmath:241:3: note: previous declaration 'float 
std::exp(float)'
 exp(float __x)
 ^
  /usr/include/c++/5/cmath: At global scope:
  /usr/include/c++/5/cmath:249:3: error: template with C linkage
 template
 ^
  /usr/include/c++/5/cmath: In function 'long double std::fabs(long double)':
  /usr/include/c++/5/cmath:264:23: error: conflicting declaration of C function 
'long double std::fabs(long double)'
 fabs(long double __x)
 ^
  /usr/include/c++/5/cmath:260:3: note: previous declaration 'float 
std::fabs(float)'
 fabs(float __x)
 ^
  /usr/include/c++/5/cmath: At global scope:
  /usr/include/c++/5/cmath:268:3: error: template with C linkage
 template
 ^
  /usr/include/c++/5/cmath: In function 'long double std::floor(long double)':
  /usr/include/c++/5/cmath:283:24: error: conflicting declaration of C function 
'long double std::floor(long double)'
 floor(long double __x)
  ^
  /usr/include/c++/5/cmath:279:3: note: previous declaration 'float 
std::floor(float)'
 floor(float __x)
 ^
  /usr/include/c++/5/cmath: At global scope:
  /usr/include/c++/5/cmath:287:3: error: template with C linkage
 template
 ^
  /usr/include/c++/5/cmath: In function 'long double std::fmod(long double, 
long double)':
  /usr/include/c++/5/cmath:302:40: error: conflicting declaration of C function 
'long double std::fmod(long double, long double)'
 fmod(long double __x, long double __y)
  ^
  /usr/include/c++/5/cmath:298:3: note: previous declaration 'float 
std::fmod(float, float)'
 fmod(float __x, float __y)
 ^
  /usr/include/c++/5/cmath: At global scope:
  /usr/include/c++/5/cmath:306:3: error: template with C linkage
 template
 ^
  /usr/include/c++/5/cmath: In function 'long double std::frexp(long double, 
int*)':
  /usr/include/c++/5/cmath:323:36: error: conflicting 

Bug#823740: marked as done (globus-io: FTBFS: test 1 accept failed: an authorization operation failed)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 13:23:45 +
with message-id 
and subject line Bug#823740: fixed in globus-xio-gsi-driver 3.9-2
has caused the Debian Bug report #823740,
regarding globus-io: FTBFS: test 1 accept failed: an authorization operation 
failed
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.)


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

globus-io fails to build from source in unstable/amd64:

  [..]

  # Client exited abnormally 255. 
  #  The following output was generated:
  # test 1 connect failed: an authentication operation failed
  # Server exited abnormally. 
  #  The following output was generated:
  # test 1 accept failed: an authentication operation failed
  ok 6 - globus-io-tcp-test-gsi-wrap-bad-creds
  # Running server:  ./globus_io_tcp_test_server  |
  # Server said listening on port 53901
  # Running client:  ./globus_io_tcp_test_client -h localhost -p 53901 -g |
  # Client exited abnormally 255. 
  #  The following output was generated:
  # test 1 connect succeeded
  # wrote large_block (1048576 bytes)
  # test1 large read failed: globus_xio: 
globus_l_xio_gsi_wrapped_buffer_to_iovec failed.
  ok 7 - globus-io-tcp-test-gsi-wrap-client-only
  # Running server:  ./globus_io_tcp_test_server -s |
  # Server said listening on port 57547
  # Running client:  ./globus_io_tcp_test_client -h localhost -p 57547 -s |
  # 
  ok 8 - globus-io-tcp-test-ssl-wrap
  # Running server:  ./globus_io_tcp_test_server -s |
  # Server said listening on port 54093
  # Running client:  ./globus_io_tcp_test_client -h localhost -p 54093 -s |
  # Client exited abnormally 255. 
  #  The following output was generated:
  # test 1 connect failed: an authentication operation failed
  # Server exited abnormally. 
  #  The following output was generated:
  # test 1 accept failed: an authentication operation failed
  ok 9 - globus-io-tcp-test-ssl-wrap-bad-cert-dir
  # Running server:  ./globus_io_tcp_test_server -s |
  # Server said listening on port 59966
  # Running client:  ./globus_io_tcp_test_client -h localhost -p 59966 -s |
  # Client exited abnormally 255. 
  #  The following output was generated:
  # test 1 connect failed: an authentication operation failed
  # Server exited abnormally. 
  #  The following output was generated:
  # test 1 accept failed: an authentication operation failed
  ok 10 - globus-io-tcp-test-ssl-wrap-bad-creds
  # Running server:  ./globus_io_tcp_test_server -s |
  # Server said listening on port 59174
  # Running client:  ./globus_io_tcp_test_client -h localhost -p 59174  |
  # Client exited abnormally 255. 
  #  The following output was generated:
  # test 1 connect succeeded
  # wrote large_block (1048576 bytes)
  # test1 large read failed: globus_xio: System error in recv: Connection reset 
by peer
  # Server exited abnormally. 
  #  The following output was generated:
  # test 1 accept succeeded
  # No delegated credential
  # Accepted connection on my socket: 127.0.0.1:59174
  # Accepted connection on my peer: 127.0.0.1:36706
  # test1 large read failed: globus_xio: 
globus_l_xio_gsi_wrapped_buffer_to_iovec failed.
  ok 11 - globus-io-tcp-test-ssl-wrap-server-only
  # Running server:  ./globus_io_tcp_test_server  |
  # Server said listening on port 40178
  # Running client:  ./globus_io_tcp_test_client -h localhost -p 40178 -s |
  # Client exited abnormally 255. 
  #  The following output was generated:
  # test 1 connect succeeded
  # wrote large_block (1048576 bytes)
  # test1 large read failed: globus_xio: System error in recv: Connection reset 
by peer
  # Server exited abnormally. 
  #  The following output was generated:
  # test 1 accept failed: an authentication operation failed
  ok 12 - globus-io-tcp-test-ssl-wrap-client-only
  # Running server:  ./globus_io_tcp_test_server -c |
  # Server said listening on port 57345
  # Running client:  ./globus_io_tcp_test_client -h localhost -p 57345 -c |
  # 
  ok 13 - globus-io-tcp-test-clear
  # Running server:  ./globus_io_tcp_test_server -c |
  # Server said listening on port 60593
  # Running client:  ./globus_io_tcp_test_client -h localhost -p 60593 -c |
  # Client exited abnormally 255. 
  #  The following output was generated:
  # test 1 connect failed: an 

Bug#822338: marked as done (upgrade from libfreeradius-client to radcli)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 12:54:44 +
with message-id 
and subject line Bug#822338: fixed in kamailio 4.4.1-1
has caused the Debian Bug report #822338,
regarding upgrade from libfreeradius-client to radcli
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.)


-- 
822338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kamailio-radius-modules
Severity: serious
Version: 4.2.0-2

kamailio-radius-modules depends on libfreeradius-client

libfreeradius-client has been deprecated in favor of radcli[1]

Please update the build dependency to use radcli. The API is fully
compatible, radcli is a fork of the previous library, it is actively
maintained and includes many bug fixes.

radcli is available in sid and jessie-backports

Please check the preinst for radcli to see if you are satisfied with it,
it has to copy /etc/radiusclient/* to /etc/radcli




1. https://packages.qa.debian.org/r/radcli.html
--- End Message ---
--- Begin Message ---
Source: kamailio
Source-Version: 4.4.1-1

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

Debian distribution maintenance software
pp.
Victor Seva  (supplier of updated kamailio 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: Wed, 11 May 2016 14:20:52 +0200
Source: kamailio
Binary: kamailio kamailio-dbg kamailio-geoip-modules kamailio-sqlite-modules 
kamailio-json-modules kamailio-memcached-modules kamailio-lua-modules 
kamailio-mono-modules kamailio-python-modules kamailio-redis-modules 
kamailio-mysql-modules kamailio-postgres-modules kamailio-cpl-modules 
kamailio-radius-modules kamailio-unixodbc-modules kamailio-presence-modules 
kamailio-perl-modules kamailio-snmpstats-modules kamailio-purple-modules 
kamailio-xmpp-modules kamailio-xml-modules kamailio-carrierroute-modules 
kamailio-berkeley-modules kamailio-berkeley-bin kamailio-ldap-modules 
kamailio-ims-modules kamailio-utils-modules kamailio-sctp-modules 
kamailio-java-modules kamailio-tls-modules kamailio-outbound-modules 
kamailio-websocket-modules kamailio-dnssec-modules kamailio-autheph-modules 
kamailio-kazoo-modules kamailio-cnxcc-modules kamailio-erlang-modules 
kamailio-extra-modules
Architecture: source amd64
Version: 4.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Victor Seva 
Description:
 kamailio   - very fast and configurable SIP proxy
 kamailio-autheph-modules - authentication using ephemeral credentials module 
for Kamailio
 kamailio-berkeley-bin - Berkeley database module for Kamailio - helper program
 kamailio-berkeley-modules - Berkeley database module for Kamailio
 kamailio-carrierroute-modules - carrierroute module for Kamailio
 kamailio-cnxcc-modules - cnxcc modules for Kamailio
 kamailio-cpl-modules - CPL module (CPL interpreter engine) for Kamailio
 kamailio-dbg - very fast and configurable SIP proxy [debug symbols]
 kamailio-dnssec-modules - contains the dnssec module
 kamailio-erlang-modules - erlang modules for Kamailio
 kamailio-extra-modules - extra modules for Kamailio
 kamailio-geoip-modules - contains the geoip module
 kamailio-ims-modules - IMS module for Kamailio
 kamailio-java-modules - contains the app_java module
 kamailio-json-modules - Json parser and jsonrpc modules for Kamailio
 kamailio-kazoo-modules - kazoo modules for Kamailio
 kamailio-ldap-modules - LDAP modules for Kamailio
 kamailio-lua-modules - contains the app_lua module
 kamailio-memcached-modules - interface to memcached server
 kamailio-mono-modules - contains the app_mono module
 kamailio-mysql-modules - MySQL database connectivity module for Kamailio
 kamailio-outbound-modules - Outbound module for Kamailio
 kamailio-perl-modules - Perl extensions and database driver for Kamailio
 kamailio-postgres-modules - PostgreSQL database connectivity module for 
Kamailio
 kamailio-presence-modules - 

Processed: your mail

[Debian Bug Tracking System]

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

> user pbuil...@packages.debian.org
Setting user to pbuil...@packages.debian.org (was mat...@debian.org).
> usertag 823651 pbuilder
There were no usertags set.
Usertags are now: pbuilder.
> severity 576425 minor
Bug #576425 [pbuilder] pbuilder: Don't fail if TMP != /tmp (aka, don't fail 
with libpam-tmpdir)
Severity set to 'minor' from 'normal'
> forcemerge 576425 725434 823651
Bug #576425 [pbuilder] pbuilder: Don't fail if TMP != /tmp (aka, don't fail 
with libpam-tmpdir)
Bug #823651 [pbuilder] pbuilder: fails to make temp file - breaks
Severity set to 'minor' from 'grave'
Marked as found in versions pbuilder/0.215 and pbuilder/0.196.
Bug #576425 [pbuilder] pbuilder: Don't fail if TMP != /tmp (aka, don't fail 
with libpam-tmpdir)
Marked as found in versions pbuilder/0.224 and pbuilder/0.215.
Added tag(s) moreinfo and unreproducible.
Bug #725434 [pbuilder] pbuilder fails with cryptic message when $TMPDIR is set 
to dir that does not exist in chroot
Marked as found in versions pbuilder/0.224 and pbuilder/0.196.
Added tag(s) unreproducible and moreinfo.
Merged 576425 725434 823651
> retitle 576425 pbuilder: fails with cryptic message when $TMPDIR/$TEMP != 
> /tmp (i.e. libpam-tmpdir)
Bug #576425 [pbuilder] pbuilder: Don't fail if TMP != /tmp (aka, don't fail 
with libpam-tmpdir)
Bug #725434 [pbuilder] pbuilder fails with cryptic message when $TMPDIR is set 
to dir that does not exist in chroot
Bug #823651 [pbuilder] pbuilder: fails to make temp file - breaks
Changed Bug title to 'pbuilder: fails with cryptic message when $TMPDIR/$TEMP 
!= /tmp (i.e. libpam-tmpdir)' from 'pbuilder: Don't fail if TMP != /tmp (aka, 
don't fail with libpam-tmpdir)'.
Changed Bug title to 'pbuilder: fails with cryptic message when $TMPDIR/$TEMP 
!= /tmp (i.e. libpam-tmpdir)' from 'pbuilder fails with cryptic message when 
$TMPDIR is set to dir that does not exist in chroot'.
Changed Bug title to 'pbuilder: fails with cryptic message when $TMPDIR/$TEMP 
!= /tmp (i.e. libpam-tmpdir)' from 'pbuilder: fails to make temp file - breaks'.
> --
Stopping processing here.

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

Bug#823651: pbuilder: fails to make temp file - breaks

[Norbert Preining]

On Sat, 07 May 2016, Norbert Preining wrote:
> > If not please provide you /etc/pbuilderrc, ~/.pbuilderrc, a full log
> > with --debug.
> 
> /etc/pbuilderrc only contains
>   MIRRORSITE=http://ftp.jaist.ac.jp/debian/
> There is no ~/.pbuilderrc.
> 
> debug log created with runing as root
>   cowbuilder --build --debug --buildresult . ...dsc
> is attached.

The problem is that TEMP is set to
/tmp/user/0/
but this directory does not exist.

$ sudo /usr/sbin/cowbuilder --login
...
I: Obtaining the cached apt archive contents
I: entering the shell
root@wienerschnitzel:/# echo $TEMP
/tmp/user/0
root@wienerschnitzel:/# ls /tmp/user/0
ls: cannot access '/tmp/user/0': No such file or directory
root@wienerschnitzel:/# 


This is *bad*, but maybe a problem of cowbuilder? I don't know.

Norbert


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

Processed: singular: fixed FTBFS but still marked as autorm

[Debian Bug Tracking System]

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

> severity 806108 important
Bug #806108 {Done: Jerome Benoit } [src:singular] 
singular: FTBFS due to indep built failure
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Reassign

[Debian Bug Tracking System]

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

> reassign 823740 globus-xio-gsi-driver 3.9-1
Bug #823740 [src:globus-io] globus-io: FTBFS: test 1 accept failed: an 
authorization operation failed
Bug reassigned from package 'src:globus-io' to 'globus-xio-gsi-driver'.
No longer marked as found in versions globus-io/11.5-1.
Ignoring request to alter fixed versions of bug #823740 to the same values 
previously set
Bug #823740 [globus-xio-gsi-driver] globus-io: FTBFS: test 1 accept failed: an 
authorization operation failed
There is no source info for the package 'globus-xio-gsi-driver' at version 
'3.9-1' with architecture ''
Unable to make a source version for version '3.9-1'
Marked as found in versions 3.9-1.
>
End of message, stopping processing here.

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

Bug#804531: eagle: cannot be rebuilt against libssl1.0.2

[Sebastian Andrzej Siewior]

On 2016-05-10 18:19:02 [-0400], Scott Howard wrote:
> I agree with this assessment. I'll raise the issue upstream. It's
> non-free, so not too high on my priority list (and not much I can do
> on my own anyways...)

Could you please open a RM bug against ftp-master? There is no need to
keep this in unstable, right? It holds back libssl1.0.0. 
Alternatively I could do it for you once I sorted most of the few other
packages that hold on to libssl1.0.0 as well…

> Thanks, everyone.
> ~Scott

Sebastian

Bug#824017: hgsubversion: uninstallable in sid

[Julien Cristau]

Source: hgsubversion
Version: 1.8.5-1
Severity: serious

Hi,

current mercurial breaks hgsubversion (<= 1.8.5-1), making it
uninstallable.

Cheers,
Julien

Bug#824018: tortoisehg: uninstallable with mercurial 3.8.x

[Julien Cristau]

Source: tortoisehg
Version: 3.7.3-1
Severity: serious

Hi,

mercurial in sid is 3.8.1-1, tortoisehg depends on mercurial (<< 3.8~),
making it uninstallable.

Cheers,
Julien

Processed: found 817852 in 1.10.18-1, found 817936 in 1.8.14-1, tagging 823984

[Debian Bug Tracking System]

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

> found 817852 1.10.18-1
Bug #817852 [liferea] liferea: Please add libpeas-1.0-python2loader to Depends
Marked as found in versions liferea/1.10.18-1.
> found 817936 1.8.14-1
Bug #817936 [src:roger-router] roger-router: Please add 
libpeas-1.0-python2loader to Depends
Marked as found in versions roger-router/1.8.14-1.
> tags 823984 + sid stretch
Bug #823984 [libarchive13] libarchive13/unstable is older than 
libarchive13/stable
Added tag(s) stretch and sid.
> thanks
Stopping processing here.

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

Bug#823984: libarchive13/unstable is older than libarchive13/stable

[Salvatore Bonaccorso]

Hi,

On Wed, May 11, 2016 at 09:50:31AM +0200, Andreas Henriksson wrote:
> Hello Vincent Lefevre.
> 
> On Wed, May 11, 2016 at 09:34:56AM +0200, Vincent Lefevre wrote:
> > On 2016-05-11 06:41:43 +0200, Salvatore Bonaccorso wrote:
> > > Please see #823893 for why this has not yet seen as well an update in
> > > unstable.
> > 
> > OK, but a decision should be made quickly. If 3.2.0 is not ready yet
> > for unstable due to potential regressions, then a patched 3.1.2 should
> > be uploaded to unstable (basically with the same as patch as stable,
> > since the current version is exactly the same as the stable version
> > before the security update). IMHO, this latter solution is probably
> > better for testing; and if users see a regression in 3.2.0, they will
> > be able to downgrade to the patched 3.1.2.
> 
> The decision to support multiple architectures and treat them all
> equally (meaning all users will have to suffer if there is problem on
> only one of them) has already been made long ago in the Debian project
> and I don't see it up for discussion, no matter how much I'd also like
> to see it change.
> See the infamous Vancouver meeting for the results of the discussion
> when this came up last time!
> 
> The only way to get this more quickly resolved is getting your hands
> dirty by helping out the kfreebsd porters and dig into investigating
> the issue there.
> See https://lists.debian.org/debian-bsd/2016/05/msg00032.html
> 
> It might be so that we simply ignore the problem on kfreebsd
> and moves on without them, given that kfreebsd-* hasn't
> qualified for being a release architecture but I'd like
> feedback on the above from porters if possible first.
> 
> Now get busy solving the problem instead of annoying people
> via the bts!

Attached is the debdiff for completeness, based on 3.1.2 in case we
want to go that route.

Regards,
Salvatore
diff -Nru libarchive-3.1.2/debian/changelog libarchive-3.1.2/debian/changelog
--- libarchive-3.1.2/debian/changelog   2015-03-05 14:54:44.0 +0100
+++ libarchive-3.1.2/debian/changelog   2016-05-11 09:45:45.0 +0200
@@ -1,3 +1,11 @@
+libarchive (3.1.2-11.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * CVE-2016-1541: heap-based buffer overflow due to improper input
+validation (Closes: #823893)
+
+ -- Salvatore Bonaccorso   Wed, 11 May 2016 09:45:09 +0200
+
 libarchive (3.1.2-11) unstable; urgency=medium
 
   * Add d/p/Add-ARCHIVE_EXTRACT_SECURE_NOABSOLUTEPATHS-option.patch
diff -Nru 
libarchive-3.1.2/debian/patches/Issue-656-Fix-CVE-2016-1541-VU-862384.patch 
libarchive-3.1.2/debian/patches/Issue-656-Fix-CVE-2016-1541-VU-862384.patch
--- libarchive-3.1.2/debian/patches/Issue-656-Fix-CVE-2016-1541-VU-862384.patch 
1970-01-01 01:00:00.0 +0100
+++ libarchive-3.1.2/debian/patches/Issue-656-Fix-CVE-2016-1541-VU-862384.patch 
2016-05-11 09:45:45.0 +0200
@@ -0,0 +1,65 @@
+From d0331e8e5b05b475f20b1f3101fe1ad772d7e7e7 Mon Sep 17 00:00:00 2001
+From: Tim Kientzle 
+Date: Sun, 24 Apr 2016 17:13:45 -0700
+Subject: [PATCH] Issue #656:  Fix CVE-2016-1541, VU#862384
+
+When reading OS X metadata entries in Zip archives that were stored
+without compression, libarchive would use the uncompressed entry size
+to allocate a buffer but would use the compressed entry size to limit
+the amount of data copied into that buffer.  Since the compressed
+and uncompressed sizes are provided by data in the archive itself,
+an attacker could manipulate these values to write data beyond
+the end of the allocated buffer.
+
+This fix provides three new checks to guard against such
+manipulation and to make libarchive generally more robust when
+handling this type of entry:
+ 1. If an OS X metadata entry is stored without compression,
+abort the entire archive if the compressed and uncompressed
+data sizes do not match.
+ 2. When sanity-checking the size of an OS X metadata entry,
+abort this entry if either the compressed or uncompressed
+size is larger than 4MB.
+ 3. When copying data into the allocated buffer, check the copy
+size against both the compressed entry size and uncompressed
+entry size.
+---
+ libarchive/archive_read_support_format_zip.c | 13 +
+ 1 file changed, 13 insertions(+)
+
+--- a/libarchive/archive_read_support_format_zip.c
 b/libarchive/archive_read_support_format_zip.c
+@@ -560,6 +560,11 @@ zip_read_mac_metadata(struct archive_rea
+ 
+   switch(rsrc->compression) {
+   case 0:  /* No compression. */
++  if (rsrc->uncompressed_size != rsrc->compressed_size) {
++  archive_set_error(>archive, 
ARCHIVE_ERRNO_FILE_FORMAT,
++  "Malformed OS X metadata entry: inconsistent size");
++  return (ARCHIVE_FATAL);
++  }
+ #ifdef HAVE_ZLIB_H
+   case 8: /* Deflate compression. */
+ #endif
+@@ -580,6 +585,12 @@ zip_read_mac_metadata(struct archive_rea
+ 

Processed: Also need to fix libzeep first

[Debian Bug Tracking System]

Processing control commands:

> block 816569 by 824013
Bug #816569 [mrs] mrs: FTBFS with GCC 6: was not declared in this scope
Bug #822466 [mrs] mrs: FTBFS: error: 'log' was not declared in this scope
816569 was blocked by: 823978
816569 was not blocking any bugs.
Added blocking bug(s) of 816569: 824013
822466 was blocked by: 823978
822466 was not blocking any bugs.
Added blocking bug(s) of 822466: 824013

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

Bug#816569: Also need to fix libzeep first

[Gert Wollny]

Control: block 816569 by 824013

The fix will have to wait until libboost1.60 becomes the default and is
build by using g++-6. In addition libzeep needs then to be fixed first
(see blocker). 

cheers, 
Gert 

Bug#823956: marked as done (php-json dependency and build-dependency issues.)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 09:54:46 +
with message-id 
and subject line Bug#823956: fixed in php-json 1.3.9-1
has caused the Debian Bug report #823956,
regarding php-json dependency and build-dependency issues.
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.)


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

Package: php5-json
Severity: serious
Version: 1.3.7-1

php5-json depends on the cruft package libjson-c2 which is no longer 
built from the json-c source package.


The release team attempted to schedule a binnmu but it was blocked due 
to the removal of dh-php5.


Furthermore even in an environment where dh-php5 is available the binnmu 
succeeds but doesn't fix the problem because the dependency is 
hardcoded. A debdiff changing the dependency is available at 
http://debdiffs.raspbian.org/main/p/php-json/php-json_1.3.7-1%2brpi1.debdiff
--- End Message ---
--- Begin Message ---
Source: php-json
Source-Version: 1.3.9-1

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php-json 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: Wed, 11 May 2016 09:56:21 +0200
Source: php-json
Binary: php5-json
Architecture: source amd64
Version: 1.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Description:
 php5-json  - JSON module for PHP 5
Closes: 816338 823956
Changes:
 php-json (1.3.9-1) unstable; urgency=medium
 .
   * Imported Upstream version 1.3.9
   * Disable --with-libjsonc option as jsonc now needs embedded library
   * Convert php-json to dh-php5-less variant, drop dependency on json-c
 (Closes: #823956)
   * Test whether /etc/php5 exists before warning about cleanup
 (Closes: #816338)
Checksums-Sha1:
 b58d43c23a3992f133ac20e007042ded84960387 2065 php-json_1.3.9-1.dsc
 6d73f73175b2c475efd65ad3a4b2464f07aea481 75383 php-json_1.3.9.orig.tar.gz
 391282addfbafdd6ba1c211513785e450684a47f 5316 php-json_1.3.9-1.debian.tar.xz
 b68ef2f0b86b3a74baca3195632b750b79aacddf 70420 
php5-json-dbgsym_1.3.9-1_amd64.deb
 f384cf7bdf2f2cde9d597ff67880efb4ba7962ea 31588 php5-json_1.3.9-1_amd64.deb
Checksums-Sha256:
 9b406f7fb642155665f3568459aa560d64001ccfe20a954c2aa50485c0bd68bd 2065 
php-json_1.3.9-1.dsc
 bc9db0e621985a9c517e956505299a0379619bc78b77e9423bee1ceaf5774934 75383 
php-json_1.3.9.orig.tar.gz
 07e5d12d18337dbe78fb46e0999f86d6f3caaac865ba316746823bcf67cf03c9 5316 
php-json_1.3.9-1.debian.tar.xz
 9876a0e050a2608a618714e86c78487f3d5105ed868fa8d6d79f748f665a381a 70420 
php5-json-dbgsym_1.3.9-1_amd64.deb
 1e90446d1cb449a4ee11e16e29c468fe8273fe6fae358fda597c950fd26d269a 31588 
php5-json_1.3.9-1_amd64.deb
Files:
 334cc2e174d691f48289cc21e07ae440 2065 php optional php-json_1.3.9-1.dsc
 b8822c1e568ee44153281cfe1cc647a0 75383 php optional php-json_1.3.9.orig.tar.gz
 8ce47c2e174e777aec1aa86efd05369a 5316 php optional 
php-json_1.3.9-1.debian.tar.xz
 5f461254f81bd4b414540445f224d10b 70420 debug extra 
php5-json-dbgsym_1.3.9-1_amd64.deb
 eef04eb71a9147686186b34b12c39b48 31588 php optional php5-json_1.3.9-1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXMuaEXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHlpMP/i5iOPWzJ37mkSmCCUQjqtja
d0RrkLjMu1RC0kElYgwizqrVwWFuiT3e+Dix2bzf/5iS4H1pSzDefF7oAm6wyL/E
PjYtwXG5+cc62mMsLpBYpavZ1uABt7sBf5CAQuePtehTxKFTexf5EZ48nV0aPHOD
RJoHKN0alZebBkALoy1ODIieu22Nvs+r3I8aw9bxthgUNRuoxwBVpxZnhBeGNAFn
SJSEUoPEQVr6svnd2IziVi+JF3d7GprSdzwF/MyBvP/3OSzL1EWGIkh5/Y2sas5x
WF/y4esHtA5WKBTg4ehlmD4eCEnusj1zEJY4HbWwgnAGO+65Vfam7V5e9ebg6KTO
wchiDo8HS11OQebVVF315O2vXlz7T0NaCr2+jQOiaeDfUKOYE3hBFzT3+RWtkxRc

Processed: Bug#824011

[Debian Bug Tracking System]

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

> found 824011 3.1.1-3
Bug #824011 [src:warzone2100] warzone2100: FTBFS in testing (maybe missing 
Build-Conflicts)
Marked as found in versions warzone2100/3.1.1-3.
> thanks
Stopping processing here.

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

Processed (with 1 error): Bug#824011

[Debian Bug Tracking System]

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

> reassign 824011 src:warzone2100
Bug #824011 [warzone2100] warzone2100: FTBFS in testing (maybe missing 
Build-Conflicts)
Bug reassigned from package 'warzone2100' to 'src:warzone2100'.
No longer marked as found in versions warzone2100/3.1.1-3.
Ignoring request to alter fixed versions of bug #824011 to the same values 
previously set
> found warzone2100 3.1.1-3
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#824011: warzone2100: FTBFS in testing (maybe missing Build-Conflicts)

[Santiago Vila]

Package: warzone2100
Version: 3.1.1-3
Severity: serious

Dear maintainer:

This package fails to build from source in stretch:

-
 debian/rules build
dh build --parallel --with autoreconf
   dh_testdir
   dh_update_autotools_config
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
dh_autoreconf ./autogen.sh
+ checking for automake >= 1.12 ... found 1.15, ok.
Sorry, automake 1.12+ is not supported yet, please use 1.11.
dh_autoreconf: ./autogen.sh returned exit code 1
debian/rules:10: recipe for target 'override_dh_autoreconf' failed
make[1]: *** [override_dh_autoreconf] Error 2
make[1]: Leaving directory '/<>'
debian/rules:7: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-

The full build log is attached.

Note: My stretch chroot has debhelper installed by default to save
some time, so it has "automake" installed by default. If the package
does not build when "automake" is installed, then it should use a
Build-Conflicts.

Thanks.

warzone2100_3.1.1-3_amd64-20160511-1125.gz
Description: application/gzip

Bug#824007: emoslib: FTBFS: No rule to make target '/usr/lib/x86_64-linux-gnu/libnetcdf.so', needed by 'usr/bin/libemos_version'

[Chris Lamb]

Source: emoslib
Version: 2:4.4.1-1
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,

emoslib fails to build from source in unstable/amd64:

  [..]

   1
  Warning: Unused variable 'cout3' declared at (1) [-Wunused-variable]
  
/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/bufrdc_wmo/buget_opera_image.F:143:0:
  
IMAGE_START=I-1
   ^
  Warning: 'image_start' may be used uninitialized in this function 
[-Wmaybe-uninitialized]
  [ 18%] Building Fortran object 
libemos-dp/CMakeFiles/emos.dir/__/bufrdc_wmo/getcode.F.o
  cd 
/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/obj-x86_64-linux-gnu/libemos-dp
 && /usr/bin/gfortran  -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" 
-DFOPEN64 -DINTEGER_IS_INT -DINTERPOL_TABLES_PATH=\"/usr/share/emos\" 
-DPOINTER_64 -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE64_SOURCE -Dgfortran -Dlinux 
-I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/obj-x86_64-linux-gnu/module
 -I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1 
-I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/obj-x86_64-linux-gnu
 
-I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/interpolation
 
-I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/bufrdc_wmo
 -I/usr/lib/include -I/usr/include -I/usr/include/hdf5/serial 
-I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7  -g -O2 
-fstack-protector-strong  -ffixed-line-length-none -fcray-pointer 
-fno-second-underscore -Wuninitialized -Wunused-variable -DSHAREDMEMORY   
-fdefault-real-8 -fdefault-double-8 -O3 -funroll-all-loops -finline-functions 
-O2 -DLITTLE_ENDIAN -J. -fPIC   -fPIC -mcmodel=medium  -c 
/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/bufrdc_wmo/getcode.F
 -o CMakeFiles/emos.dir/__/bufrdc_wmo/getcode.F.o
  f951: Warning: Nonexistent include directory '/usr/lib/include' 
[-Wmissing-include-dirs]
  f951: Warning: Nonexistent include directory '/usr/include/hdf5/serial' 
[-Wmissing-include-dirs]
  f951: Warning: Nonexistent include directory '/usr/include/python2.7' 
[-Wmissing-include-dirs]
  f951: Warning: Nonexistent include directory 
'/usr/include/x86_64-linux-gnu/python2.7' [-Wmissing-include-dirs]
  
/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/bufrdc_wmo/getcode.F:106:0:
  
201  ycode(ii:ii+iz-1)=ctext(j)(1:iz)
   ^
  Warning: 'iz' may be used uninitialized in this function 
[-Wmaybe-uninitialized]
  
/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/bufrdc_wmo/getcode.F:102:0:
  
  iz=k
   ^
  note: 'iz' was declared here
  [ 18%] Building Fortran object 
libemos-dp/CMakeFiles/emos.dir/__/bufrdc_wmo/getflag.F.o
  cd 
/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/obj-x86_64-linux-gnu/libemos-dp
 && /usr/bin/gfortran  -DBUFR_TABLES_PATH=\"/usr/share/emos/bufrtables\" 
-DFOPEN64 -DINTEGER_IS_INT -DINTERPOL_TABLES_PATH=\"/usr/share/emos\" 
-DPOINTER_64 -DREAL_8 -DREAL_BIGGER_THAN_INTEGER -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE64_SOURCE -Dgfortran -Dlinux 
-I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/obj-x86_64-linux-gnu/module
 -I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1 
-I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/obj-x86_64-linux-gnu
 
-I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/interpolation
 
-I/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/bufrdc_wmo
 -I/usr/lib/include -I/usr/include -I/usr/include/hdf5/serial 
-I/usr/include/python2.7 -I/usr/include/x86_64-linux-gnu/python2.7  -g -O2 
-fstack-protector-strong  -ffixed-line-length-none -fcray-pointer 
-fno-second-underscore -Wuninitialized -Wunused-variable -DSHAREDMEMORY   
-fdefault-real-8 -fdefault-double-8 -O3 -funroll-all-loops -finline-functions 
-O2 -DLITTLE_ENDIAN -J. -fPIC   -fPIC -mcmodel=medium  -c 
/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/bufrdc_wmo/getflag.F
 -o CMakeFiles/emos.dir/__/bufrdc_wmo/getflag.F.o
  f951: Warning: Nonexistent include directory '/usr/lib/include' 
[-Wmissing-include-dirs]
  f951: Warning: Nonexistent include directory '/usr/include/hdf5/serial' 
[-Wmissing-include-dirs]
  f951: Warning: Nonexistent include directory '/usr/include/python2.7' 
[-Wmissing-include-dirs]
  f951: Warning: Nonexistent include directory 
'/usr/include/x86_64-linux-gnu/python2.7' [-Wmissing-include-dirs]
  [ 18%] Building Fortran object 
libemos-dp/CMakeFiles/emos.dir/__/bufrdc_wmo/bu_check_s4s.F.o
  cd 
/home/lamby/temp/cdt.20160511095054.RcEn9womis.emoslib/emoslib-4.4.1/obj-x86_64-linux-gnu/libemos-dp
 && /usr/bin/gfortran  

Bug#824008: python-xdo: FTBFS: ImportError: No module named 'six'

[Chris Lamb]

Source: python-xdo
Version: 0.3-1
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,

python-xdo fails to build from source in unstable/amd64:

  [..]

  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'python-xdo-build-deps' in 
'../python-xdo-build-deps_0.3-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package python-xdo-build-deps.
  (Reading database ... 23076 files and directories currently installed.)
  Preparing to unpack python-xdo-build-deps_0.3-1_all.deb ...
  Unpacking python-xdo-build-deps (0.3-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxdo3 libxext6 libxi6
libxinerama1 libxkbcommon0 libxtst6 python-all python-setuptools python3-all
python3-pkg-resources python3-setuptools x11-common xkb-data
  Suggested packages:
python-setuptools-doc
  The following NEW packages will be installed:
libx11-6 libx11-data libxau6 libxcb1 libxdmcp6 libxdo3 libxext6 libxi6
libxinerama1 libxkbcommon0 libxtst6 python-all python-setuptools python3-all
python3-pkg-resources python3-setuptools x11-common xkb-data
  0 upgraded, 18 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 2607 kB of archives.
  After this operation, 11.8 MB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 libxau6 amd64 
1:1.0.8-1 [20.7 kB]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 libxdmcp6 amd64 
1:1.1.2-1.1 [26.2 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libxcb1 amd64 
1.11.1-1 [44.1 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libx11-data all 
2:1.6.3-1 [128 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libx11-6 amd64 
2:1.6.3-1 [742 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libxext6 amd64 
2:1.3.3-1 [52.7 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libxinerama1 amd64 
2:1.1.3-1+b1 [16.9 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 xkb-data all 2.17-1 
[627 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 libxkbcommon0 amd64 
0.5.0-1 [121 kB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 libxi6 amd64 
2:1.7.6-1 [80.6 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 x11-common all 
1:7.7+15 [251 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 libxtst6 amd64 
2:1.2.2-1+b1 [27.3 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 libxdo3 amd64 
1:3.20150503.1-2 [32.2 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 python-all amd64 
2.7.11-1 [936 B]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 python-setuptools 
all 20.10.1-1 [203 kB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 python3-all amd64 
3.5.1-3 [936 B]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 
python3-pkg-resources all 20.10.1-1 [112 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 python3-setuptools 
all 20.10.1-1 [122 kB]
  Fetched 2607 kB in 0s (36.7 MB/s)
  Selecting previously unselected package libxau6:amd64.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 23080 files and directories currently installed.)
  Preparing to unpack .../libxau6_1%3a1.0.8-1_amd64.deb ...
  Unpacking libxau6:amd64 (1:1.0.8-1) ...
  Selecting previously unselected package libxdmcp6:amd64.
  Preparing to unpack .../libxdmcp6_1%3a1.1.2-1.1_amd64.deb ...
  Unpacking libxdmcp6:amd64 (1:1.1.2-1.1) ...
  Selecting previously unselected package libxcb1:amd64.
  Preparing to unpack .../libxcb1_1.11.1-1_amd64.deb ...
  Unpacking libxcb1:amd64 (1.11.1-1) ...
  Selecting previously unselected package libx11-data.
  Preparing to unpack .../libx11-data_2%3a1.6.3-1_all.deb ...
  Unpacking libx11-data (2:1.6.3-1) ...
  Selecting previously unselected package 

Processed: Re: Bug#823981: RFS: aiksaurus/1.2.1+dev-0.12-6.3 [RC] [NMU] -- an English-language thesaurus

[Debian Bug Tracking System]

Processing control commands:

> owner 823981 !
Bug #823981 [sponsorship-requests] RFS: aiksaurus/1.2.1+dev-0.12-6.3 [RC] [NMU] 
-- an English-language thesaurus
Owner recorded as Gianfranco Costamagna .
> tags -1 pending
Bug #817290 [src:aiksaurus] aiksaurus: Removal of dh_desktop
Added tag(s) pending.

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

Bug#817290: Bug#823981: RFS: aiksaurus/1.2.1+dev-0.12-6.3 [RC] [NMU] -- an English-language thesaurus

[Gianfranco Costamagna]

control: owner 823981 !
control: tags -1 pending

Hi,
just WOW.

changes were HUGE, but needed.

Unfortunately I had to do some additional work on top of your changes

e.g. you changed the orig tarball, this isn't possible unless you rename it.
so I extracted the current "patch" inside the tarball, into an additional 
patch, and
rebased your work on top of that (one patch refreshed, one deleted).

I deleted from the current patch the config.* changes, useless with autoreconf


I also tweaked the changelog to be a little bit more verbose, and probably 
something more
I put this on deferred/15, and I'm attaching it to this email or you can dget 
from there
http://debomatic-amd64.debian.net/debomatic/unstable/pool/aiksaurus_1.2.1+dev-0.12-6.3/aiksaurus_1.2.1+dev-0.12-6.3_amd64.changes
please let me know if it sounds good for you!

also, your line closing bugs was missing a semicolon, vim wasn't highlighting 
the second bug
(I'm not sure if the bug would have been closed correctly or not)

thanks for your contribution to Debian!

Gianfranco

aiksaurus_1.2.1+dev-0.12-6.3.debian.tar.xz
Description: application/xz

Processed: found 815797 in php5/5.6.21+dfsg-1

[Debian Bug Tracking System]

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

> found 815797 php5/5.6.21+dfsg-1
Bug #815797 [src:php5] PHP 7.0 Transition Blocker Bug
Marked as found in versions php5/5.6.21+dfsg-1.
> thanks
Stopping processing here.

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

Bug#823984: libarchive13/unstable is older than libarchive13/stable

[Andreas Henriksson]

Hello Vincent Lefevre.

On Wed, May 11, 2016 at 09:34:56AM +0200, Vincent Lefevre wrote:
> On 2016-05-11 06:41:43 +0200, Salvatore Bonaccorso wrote:
> > Please see #823893 for why this has not yet seen as well an update in
> > unstable.
> 
> OK, but a decision should be made quickly. If 3.2.0 is not ready yet
> for unstable due to potential regressions, then a patched 3.1.2 should
> be uploaded to unstable (basically with the same as patch as stable,
> since the current version is exactly the same as the stable version
> before the security update). IMHO, this latter solution is probably
> better for testing; and if users see a regression in 3.2.0, they will
> be able to downgrade to the patched 3.1.2.

The decision to support multiple architectures and treat them all
equally (meaning all users will have to suffer if there is problem on
only one of them) has already been made long ago in the Debian project
and I don't see it up for discussion, no matter how much I'd also like
to see it change.
See the infamous Vancouver meeting for the results of the discussion
when this came up last time!

The only way to get this more quickly resolved is getting your hands
dirty by helping out the kfreebsd porters and dig into investigating
the issue there.
See https://lists.debian.org/debian-bsd/2016/05/msg00032.html

It might be so that we simply ignore the problem on kfreebsd
and moves on without them, given that kfreebsd-* hasn't
qualified for being a release architecture but I'd like
feedback on the above from porters if possible first.

Now get busy solving the problem instead of annoying people
via the bts!

Regards,
Andreas Henriksson

Bug#819538: marked as done (gnome-builder: build against vala 0.32)

[Debian Bug Tracking System]

Your message dated Wed, 11 May 2016 07:49:29 +
with message-id 
and subject line Bug#819538: fixed in gnome-builder 3.20.2-1
has caused the Debian Bug report #819538,
regarding gnome-builder: build against vala 0.32
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.)


-- 
819538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-builder
Version: 3.18.1-2
Severity: serious

Your package needs to be updated to build against the new vala
0.32.

Cheers,
Emilio
--- End Message ---
--- Begin Message ---
Source: gnome-builder
Source-Version: 3.20.2-1

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated gnome-builder 
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: Wed, 11 May 2016 09:22:28 +0200
Source: gnome-builder
Binary: gnome-builder
Architecture: source amd64
Version: 3.20.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Andreas Henriksson 
Description:
 gnome-builder - IDE for GNOME
Closes: 819538
Changes:
 gnome-builder (3.20.2-1) unstable; urgency=medium
 .
   [ Andreas Henriksson ]
   * New upstream release.
   * Drop debian/patches/0001-vala-remove-in-tree-hack-for-builder-deps.patch
 - merged upstream.
   * Update build-dependencies according to configure.ac changes:
 - Bump gobject-introspection to >= 1.47.92
 - Bump libglib2.0-dev to >= 2.47.92
 - Bump libgtk-3-dev to >= 3.20.0
 - Bump libgtksourceview-3.0-dev to >= 3.20.0
 - Bump libpeas-dev to >= 1.17.0
 - Bump python-gi-dev to >= 3.19.3
 - Bump valac to >= 0.30.0.55
 - Add yelp-tools
   * Change dependency from valac-0.30-vapi to valac-0.32-vapi
 (Closes: #819538)
   * Change libvala-0.30-dev build-dependency to -0.32 to match.
   * Bump Standards-Version to 3.9.8
   * Ship new gnome-builder-worker and ide commands
   * Ship new help files
   * Add debian/patches/fix-terminal-plugin-ldflags.patch
 - avoids generating so-versioned libterminal.so.*
   * debian/rules: delete all *.pyc (and *.pyo) files in usr/lib
 - avoids precompiled site-packages python files in package.
   * debian/rules: delete usr/include/gnome-builder-*
 - files exists to allow gir, vala, etc bindings generation in-tree.
   * Install usr/lib/python3.5/site-packages/gi/overrides for Ide.py override
 - see also http://bugs.debian.org/819736
   * Use dh-autoreconf, needed since we patch plugins/terminal/Makefile.am
 - this replaces autotools-dev which gets dropped
   * Explicitly enable git plugin (which was formerly not a plugin)
   * Bump build-dependencies for plugins/*/configure.ac changes:
 - devhelp plugin: libdevhelp-dev to >= 3.20.0
 - git plugin: libgit2-glib-1.0-dev to >= 0.24.0
 Note: added/new plugins not taken into consideration here (yet).
   * Add debian/patches/fix-missing-git-check.patch
   * Drop explicit disabling of device-manager plugin, removed upstream.
   * Explicitly enable all new plugins:
 - build-tools-plugin, comment-code-plugin, contributing-plugin,
   create-project-plugin, fpaste-plugin, gcc-plugin, gettext-plugin,
   jhbuild-plugin, library-template-plugin, project-tree-plugin,
   support-plugin, todo-plugin, xdg-app-plugin
   * Build-dep on dh-python, use --with python3 and dep on ${python3:Depends}.
 - according to man dh_python3 for fixing up module path.
   * Remove gi override pycache and use py3compile in postinst.
   * Bump libpeas build-dependency as we need 1.18.0 at runtime
 - otherwise the main 'editor' plugin will not be found and all breaks.
 .
   [ Michael Biebl ]
   * Drop uploaders.mk from debian/rules as this breaks the clean target with
 dh. Instead use the gnome dh addon which updates debian/control via
 

Bug#823984: libarchive13/unstable is older than libarchive13/stable

[Vincent Lefevre]

On 2016-05-11 06:41:43 +0200, Salvatore Bonaccorso wrote:
> Please see #823893 for why this has not yet seen as well an update in
> unstable.

OK, but a decision should be made quickly. If 3.2.0 is not ready yet
for unstable due to potential regressions, then a patched 3.1.2 should
be uploaded to unstable (basically with the same as patch as stable,
since the current version is exactly the same as the stable version
before the security update). IMHO, this latter solution is probably
better for testing; and if users see a regression in 3.2.0, they will
be able to downgrade to the patched 3.1.2.

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