Processed: Re: libgda5: FTBFS: tests failures annotations:

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #839444 [src:libgda5] libgda5: FTBFS: tests failures annotations:
Severity set to 'important' from 'serious'
> tags -1 + unreproducible moreinfo
Bug #839444 [src:libgda5] libgda5: FTBFS: tests failures annotations:
Added tag(s) moreinfo and unreproducible.

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

Bug#839444: libgda5: FTBFS: tests failures annotations:

[Andreas Henriksson]

Control: severity -1 important
Control: tags -1 + unreproducible moreinfo

Hello Lucas Nussbaum

Thanks for your bug report.

On Sat, Oct 01, 2016 at 04:12:57PM +0200, Lucas Nussbaum wrote:
> Source: libgda5
> Version: 5.2.4-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20161001 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
 > PASS: check_model_import
> > PASS: check_virtual
> > ../../test-driver: line 107: 29666 Segmentation fault  "$@" > $log_file 
> > 2>&1
> > FAIL: check_data_proxy
[]


Unfortunately I'm not able to reproduce the problem here. It also built
fine on the official buildds so I'm downgrading the severity for now.

If you can reproduce the problem, please provide a backtrace from the
segmentation fault.

Regards,
Andreas Henriksson

Bug#839567: rake does not work with jruby

[Helmut Grohne]

On Mon, Oct 03, 2016 at 04:46:11PM -0700, tony mancill wrote:
> I agree with Helmut's suggestion that jruby should drop the Provides.
> Even if there are contexts in which jruby could act as a ruby
> interpreter, I don't think we should encourage our users to use it
> when we have ruby available.  Or put another way, if you're using
> jruby, it typically to solve a specific problem or because you have
> special considerations about your runtime environment, not because
> you're looking for a general purpose Ruby interpreter.

I think the implications of having jruby drop ruby-interpreter deserve
more thought from the ruby team.

It appears to me that jruby would just work with a fair amount of ruby
modules[1]. Yet, after dropping that provides, trying to install e.g.
jruby and ruby-text will also pull in another ruby implementation. So it
seems to me that the virtual package ruby-interpreter has actually been
used with two very different meanings which is now causing the problem:
One meaning is to provide /usr/bin/ruby and the other is a means to
execute ruby code. At the moment, jruby clearly doesn't do the former,
but still does the latter.

The Perl world has evaded this issue by not having a secondary
implementation (that is considered ready to use with existing modules).

The Python world has "solved" this issue by packaging each and every
module (in addition to extensions) for all of the interpreters. For a
module foo, we now have python-foo, python3-foo and pypy-foo (in the
worst case, e.g. -six, -wand, -pkg-resources, ...).

Please consider learning from them and - if possible - choosing a
different approach here. Consider employing a different policy that
makes the aforementioned combination feasible:

1. Every package that actually invokes ruby (as opposed to using ruby
   libraries through its own library interface) must depend on a ruby
   implementation (e.g. ruby | ruby-interpreter, or possibly an
   embedded interpreter if applicable).

2. Given that all invocation points must depend on an interpreter, ruby
   modules should not depend on a ruby-interpreter unless they require a
   particular implementation.

It seems like 1. is mostly in place already. I just note it here,
because 2. breaks badly if 1. is violated. Let me also clarify that a
module can require a particular implementation by using a ruby
extension, so the beauty mostly vanishes on the first extension in the
dependency tree. It also seems that 2. is partially in place (e.g.
ruby-power-assert, ruby-test-unit, but not ruby-text, ruby-wirble,
ruby-formatador, ...). So what I am requesting might already be policy,
but isn't fully implemented yet.

The Multi-Arch nerd over here also notes that this way allows annotating
a significant chunk of ruby modules with Multi-Arch: foreign and that
tracker.d.o will tell you where (e.g. ruby-rd).

The node people have recently started looking into Multi-Arch and
noticed that maybe having every node module depend on nodejs was not the
best approach.

Helmut

[1] Let me use the typical Perl and Python terminology here: We call
libraries "modules" if they are source-only and we call them
"extensions" if they produce architecture-specific artifacts such as
shared libraries loaded into an interpreter.

Bug#839354: guitarix: FTBFS: ../src/gx_head/engine/ladspaback.cpp:1625:61: error: no match for 'operator!=' (operand types are 'Glib::RefPtr' and 'int')

[Hermann Meyer]

> ../src/gx_head/engine/ladspaback.cpp:1625:61: error: no match for 'operator!=' 
(operand types are 'Glib::RefPtr' and 'int')
>  while ((file_info = child_enumeration->next_file()) != 0) {
> ~^~~~



Hi

Even if I cant reproduce the build failure here locally, I notice that 
the comparison against 0 isn't really needed.


Find attached a patch to fix that.

regards
hermann
diff --git a/trunk/src/gx_head/engine/ladspaback.cpp b/trunk/src/gx_head/engine/ladspaback.cpp
index 2a6bd01..be934a7 100644
--- a/trunk/src/gx_head/engine/ladspaback.cpp
+++ b/trunk/src/gx_head/engine/ladspaback.cpp
@@ -1622,7 +1622,7 @@ void LadspaPluginList::load(gx_system::CmdlineOptions& options, std::vector file_info;
 
-while ((file_info = child_enumeration->next_file()) != 0) {
+while ((file_info = child_enumeration->next_file())) {
 if (file_info->get_attribute_string(G_FILE_ATTRIBUTE_STANDARD_FAST_CONTENT_TYPE) == "application/x-sharedlib") {
 std::string nm = file_info->get_attribute_byte_string(G_FILE_ATTRIBUTE_STANDARD_NAME);
 if (lib_is_blacklisted(nm)) {
@@ -1650,7 +1650,7 @@ void LadspaPluginList::load(gx_system::CmdlineOptions& options, std::vector file_info;
 
-while ((file_info = child_enumeration->next_file()) != 0) {
+while ((file_info = child_enumeration->next_file())) {
 	//if not f.endswith((".rdf",".rdfs")):
 if (file_info->get_attribute_string(G_FILE_ATTRIBUTE_STANDARD_FAST_CONTENT_TYPE) == "application/rdf+xml") {
 std::string nm = file_info->get_attribute_byte_string(G_FILE_ATTRIBUTE_STANDARD_NAME);

Processed: your mail

[Debian Bug Tracking System]

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

> notfixed 835742 0.0~git20160413-1
Bug #835742 {Done: Tim Potter } [src:golang-google-cloud] 
golang-google-cloud: FTBFS: dh_auto_build: go install -v -p 1 
google.golang.org/cloud google.golang.org/cloud/bigquery 
google.golang.org/cloud/bigtable google.golang.org/cloud/bigtable/bttest 
google.golang.org/cloud/bigtable/cmd/cbt 
google.golang.org/cloud/bigtable/cmd/loadtest 
google.golang.org/cloud/bigtable/internal/cbtrc 
google.golang.org/cloud/bigtable/internal/cluster_data_proto 
google.golang.org/cloud/bigtable/internal/cluster_service_proto 
google.golang.org/cloud/bigtable/internal/data_proto 
google.golang.org/cloud/bigtable/internal/duration_proto 
google.golang.org/cloud/bigtable/internal/empty 
google.golang.org/cloud/bigtable/internal/service_proto 
google.golang.org/cloud/bigtable/internal/table_data_proto 
google.golang.org/cloud/bigtable/internal/table_service_proto 
google.golang.org/cloud/compute/metadata google.golang.org/cloud/container 
google.golang.org/cloud/datastore 
google.golang.org/cloud/datastore/internal/proto 
google.golang.org/cloud/datastore/internal/type_proto 
google.golang.org/cloud/examples/bigquery/concat_table 
google.golang.org/cloud/examples/bigquery/load 
google.golang.org/cloud/examples/bigquery/query 
google.golang.org/cloud/examples/bigquery/read 
google.golang.org/cloud/examples/bigtable/bigtable-hello 
google.golang.org/cloud/examples/bigtable/search 
google.golang.org/cloud/examples/pubsub/cmdline 
google.golang.org/cloud/examples/pubsub/consumer 
google.golang.org/cloud/examples/storage/appengine 
google.golang.org/cloud/examples/storage/appenginevm 
google.golang.org/cloud/internal google.golang.org/cloud/internal/opts 
google.golang.org/cloud/internal/testutil 
google.golang.org/cloud/internal/transport google.golang.org/cloud/logging 
google.golang.org/cloud/pubsub google.golang.org/cloud/storage returned exit 
code 2
Ignoring request to alter fixed versions of bug #835742 to the same values 
previously set
>
End of message, stopping processing here.

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

Processed: tagging 839159

[Debian Bug Tracking System]

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

> tags 839159 + unreproducible moreinfo
Bug #839159 [gnucash] gnucash: does not accept any input except letters and 
numbers
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Bug#839159: gnucash: does not accept any input except letters and numbers

[Dmitry Smirnov]

On Thursday, 29 September 2016 5:23:17 PM AEDT Dominik George wrote:
> I cannot type anything except letters and numbers anymore, e.g.
> backspace does not delete text when it should, Ctrl-C and Ctrl-V do not
> work, PgUP and PgDwn do not scroll anymore…

Which Desktop Environment exhibit this problem? I'm unable to reproduce on 
Cinnamon and KDE as well as over "ssh -X"... Could it be related to #815005?

-- 
Regards,
 Dmitry Smirnov.

---

Belief means not wanting to know what is true.
-- Friedrich Nietzsche


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

Processed: severity of 839159 is important

[Debian Bug Tracking System]

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

> severity 839159 important
Bug #839159 [gnucash] gnucash: does not accept any input except letters and 
numbers
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: just upgrade to new upstream

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +fixed-upstream
Bug #822369 [xfsprogs] xfsprogs: FTBFS: error: redefinition of 'struct fsxattr'
Bug #822470 [xfsprogs] qemu: FTBFS: error: redefinition of 'struct fsxattr'
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.

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

Bug#822369: just upgrade to new upstream

[Adam Borowski]

Control: tags -1 +fixed-upstream

It has been long since fixed in modern upstream releases.  Debian is stuck
at 4.3, upstream has 4.7 and 4.8-rc3.  Obviously, stuff that's closely tied
to kernel headers is likely to break when there's a big discrepancy between
versions.

Please update!

-- 
A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol, 1kg
raspberries, 0.4kg sugar; put into a big jar for 1 month.  Filter out and
throw away the fruits (can dump them into a cake, etc), let the drink age
at least 3-6 months.

Bug#839567: rake does not work with jruby

[Christian Hofstaedtler]

* Helmut Grohne  [161003 23:10]:
> On Mon, Oct 03, 2016 at 11:13:13AM +0200, Emmanuel Bourg wrote:
> > What is the expected contract for a package providing ruby-interpreter?
> 
> I wish I could tell. Judging from
> https://wiki.debian.org/Teams/Ruby/Packaging, it seems that
> ruby-interpreter requires /usr/bin/ruby. Not sure how official that is.
> 
> > Do it just have to offer a /usr/bin/ruby alternative?

Given that ruby-interpreter is listed as an alternative to ruby,
anything that provides ruby-interpreter needs to have at least all
the binaries from ruby. The harder part is actually having these
binaries work with the libraries that depend on ruby-interpreter.
(They are installed into shared and/or versioned directories and may
ship .so files.)

> I'm not sure we currently support non-default ruby implementations.
> Which indicates that jruby should simply drop the provides.

I do not think it is feasible today to ship a ruby implementation
that provides ruby-interpreter without (some form of) support in
gem2deb.

Best is probably to just drop the Provides in jruby.

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

Bug#806660: marked as done (taglib: FTBFS when built with dpkg-buildpackage -A (unable to chdir to builddir))

[Debian Bug Tracking System]

Your message dated Tue, 04 Oct 2016 00:33:45 +
with message-id 
and subject line Bug#806660: fixed in taglib 1.11+dfsg.1-0.1
has caused the Debian Bug report #806660,
regarding taglib: FTBFS when built with dpkg-buildpackage -A (unable to chdir 
to builddir)
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.)


-- 
806660: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:taglib
Version: 1.9.1-2.4
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
# build-indep gets invoked in buildds as well...
if [ -x /usr/bin/doxygen ]; then \
dh_auto_build --buildsystem=makefile --builddirectory=builddir -- docs; \
fi
dh_auto_build: error: unable to chdir to builddir
debian/rules:29: recipe for target 'builddir/doc/html/index.html' failed
make: *** [builddir/doc/html/index.html] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.
--- End Message ---
--- Begin Message ---
Source: taglib
Source-Version: 1.11+dfsg.1-0.1

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

Debian distribution maintenance software
pp.
Matteo Cypriani  (supplier of updated taglib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Sep 2016 16:39:42 -0400
Source: taglib
Binary: libtag1v5 libtag1v5-vanilla libtag1-dev libtag1-doc libtagc0 
libtagc0-dev
Architecture: source amd64 all
Version: 1.11+dfsg.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Modestas Vainius 
Changed-By: Matteo Cypriani 
Description:
 libtag1-dev - audio meta-data library - development files
 libtag1-doc - audio meta-data library - API documentation
 libtag1v5  - audio meta-data library
 libtag1v5-vanilla - audio meta-data library - vanilla flavour
 libtagc0   - audio meta-data library - C bindings
 libtagc0-dev - audio meta-data library - development files for C bindings
Closes: 730206 736188 805848 806660
Changes:
 taglib (1.11+dfsg.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Modestas Vainius ]
   * Get rid of 'static libraries' from package descriptions. This is not true
 anyway (if it has ever been). See #639104.
 .
   [ Matteo Cypriani ]
   * New upstream version 1.11 (Closes: #805848, #730206).
   * Repack upstream tarball to get rid of non-free file id3v22-tda.mp3,
 see README.Debian-source (Closes: #736188).
   * Drop patch multiarch.diff (applied upstream).
   * Bump Standards-Version to 3.9.8 (no changes needed).
   * Fix debian/watch.
   * Update debian/copyright and switch to DEP-5 format.
   * debian/control:
 + Update VCS URIs to the new collab-maint repository.
 + Build-Depend on libboost-dev.
 + Remove unneeded versions in Build-Depends.
   * debian/rules:
 + Call cmake with BUILD_SHARED_LIBS.
 + Use DEB_BUILD_MAINT_OPTIONS to enforce hardening.
 + use override_dh_auto_build-indep target instead of build-indep to
   generate the documentation (Closes: #806660).
   * Update symbols.
   * Don't install md5 

Bug#839567: rake does not work with jruby

[tony mancill]

I agree with Helmut's suggestion that jruby should drop the Provides.
Even if there are contexts in which jruby could act as a ruby
interpreter, I don't think we should encourage our users to use it
when we have ruby available.  Or put another way, if you're using
jruby, it typically to solve a specific problem or because you have
special considerations about your runtime environment, not because
you're looking for a general purpose Ruby interpreter.

If there are no objections, I'll prepare an upload of jruby that drops
the Provides of ruby-interpreter.

Bug#839364: [pkg-golang-devel] Bug#839364: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Tianon Gravi]

On 3 October 2016 at 15:49, Tianon Gravi  wrote:
> Oh dur, good point.  src:golang-defaults took over all the binaries
> from src:golang; I'll file an FTP team bug.

#839690 :)


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#839364: [pkg-golang-devel] Bug#839364: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Michael Hudson-Doyle]

On 4 October 2016 at 11:25, Tianon Gravi  wrote:

> On 1 October 2016 at 01:49, Lucas Nussbaum  wrote:
> > Source: golang
> > Version: 2:1.6.1-2
> > Severity: serious
> > Tags: stretch sid
> > User: debian...@lists.debian.org
> > Usertags: qa-ftbfs-20160930 qa-ftbfs
> > Justification: FTBFS on amd64
>
> I'm honestly confused about where this one is coming from. :(
>
> The current version of src:golang in both sid and stretch is 2:1.7~1,
> and the contents of it are simple metapackages which shouldn't have
> any difficulty building.


That's src:golang-defaults, isn't it?


> Is there some cruft in the archive we need
> to ask the FTP team to take care of that's causing this older version
> to get included in the rebuild?
>

I think src:golang may need deleting. Haven't checked.

Cheers,
mwh

Bug#839364: [pkg-golang-devel] Bug#839364: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Tianon Gravi]

On 3 October 2016 at 15:47, Michael Hudson-Doyle
 wrote:
> That's src:golang-defaults, isn't it?
>
>>
>> Is there some cruft in the archive we need
>> to ask the FTP team to take care of that's causing this older version
>> to get included in the rebuild?
>
>
> I think src:golang may need deleting. Haven't checked.

Oh dur, good point.  src:golang-defaults took over all the binaries
from src:golang; I'll file an FTP team bug.


♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#839010: reopen bug

[Aleksi Suhonen]

Hi,

Bug 839010 was filed against Debian/stable AND Debian/unstable. There is 
a fix for the stable package, but according to the opening statement of 
the bug, it is still found in the unstable package at version 
1:9.10.3.dfsg.P4-10.1, which is the newest package version in unstable.


So the bug cannot be closed until it has been fixed in both branches. 
1:9.9.5.dfsg-9+deb8u7 doesn't upgrade 1:9.10.3.dfsg.P4-10.1.   What am I 
missing?


--
Aleksi Suhonen

() ascii ribbon campaign
/\ support plain text e-mail

Bug#839317: marked as done (golang-1.7: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 22:38:08 +
with message-id 
and subject line Bug#839317: fixed in golang-1.7 1.7.1-3
has caused the Debian Bug report #839317,
regarding golang-1.7: FTBFS: tests 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.)


-- 
839317: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-1.7
Version: 1.7.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> set -ex; \
>   cd src; \
>   export PATH="/<>/bin:$PATH"; \
>   eval "$(go tool dist env)"; \
>   bash run.bash -k -no-rebuild;
> + cd src
> + export 
> PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + go tool dist env
> + eval CC="gcc"
> CC_FOR_TARGET="gcc"
> GOROOT="/<>"
> GOBIN="/<>/bin"
> GOARCH="amd64"
> GOOS="linux"
> GOHOSTARCH="amd64"
> GOHOSTOS="linux"
> GOTOOLDIR="/<>/pkg/tool/linux_amd64"
> + CC=gcc
> + CC_FOR_TARGET=gcc
> + GOROOT=/<>
> + GOBIN=/<>/bin
> + GOARCH=amd64
> + GOOS=linux
> + GOHOSTARCH=amd64
> + GOHOSTOS=linux
> + GOTOOLDIR=/<>/pkg/tool/linux_amd64
> + bash run.bash -k -no-rebuild
> 
> # Testing packages.
> okarchive/tar 0.026s
> okarchive/zip 0.067s
> okbufio   0.069s
> okbytes   0.137s
> okcompress/bzip2  0.070s
> okcompress/flate  1.084s
> okcompress/gzip   0.008s
> okcompress/lzw0.004s
> okcompress/zlib   0.025s
> okcontainer/heap  0.009s
> okcontainer/list  0.019s
> okcontainer/ring  0.013s
> okcontext 0.938s
> okcrypto/aes  0.026s
> okcrypto/cipher   0.003s
> okcrypto/des  0.008s
> okcrypto/dsa  0.003s
> okcrypto/ecdsa0.115s
> okcrypto/elliptic 0.045s
> okcrypto/hmac 0.004s
> okcrypto/md5  0.003s
> okcrypto/rand 0.024s
> okcrypto/rc4  0.109s
> okcrypto/rsa  0.109s
> okcrypto/sha1 0.043s
> okcrypto/sha256   0.014s
> okcrypto/sha512   0.010s
> okcrypto/subtle   0.005s
> okcrypto/tls  1.069s
> okcrypto/x509 0.873s
> okdatabase/sql0.045s
> okdatabase/sql/driver 0.007s
> okdebug/dwarf 0.009s
> okdebug/elf   0.025s
> okdebug/gosym 0.241s
> okdebug/macho 0.014s
> okdebug/pe0.019s
> okdebug/plan9obj  0.014s
> okencoding/ascii850.002s
> okencoding/asn1   0.003s
> okencoding/base32 0.006s
> okencoding/base64 0.012s
> okencoding/binary 0.003s
> okencoding/csv0.003s
> okencoding/gob0.062s
> okencoding/hex0.010s
> okencoding/json   0.226s
> okencoding/pem0.015s
> okencoding/xml0.015s
> okerrors  0.002s
> okexpvar  0.004s
> okflag0.012s
> okfmt 0.120s
> okgo/ast  0.011s
> okgo/build0.072s
> okgo/constant 0.004s
> okgo/doc  0.044s
> okgo/format   0.008s
> okgo/internal/gccgoimporter   0.011s
> okgo/internal/gcimporter  0.402s
> okgo/parser   0.042s
> okgo/printer  0.421s
> okgo/scanner  0.004s
> okgo/token0.025s
> okgo/types0.619s
> okhash/adler320.010s
> okhash/crc32  0.004s
> okhash/crc64  0.009s
> okhash/fnv0.005s
> okhtml0.003s
> okhtml/template   0.041s
> okimage   0.148s
> okimage/color 0.080s
> okimage/draw  0.084s
> okimage/gif   0.122s
> okimage/jpeg  0.162s
> okimage/png   0.046s
> okindex/suffixarray   0.006s
> okinternal/singleflight   0.017s
> okinternal/trace  0.030s
> okio  0.020s
> okio/ioutil   0.013s
> oklog 0.008s
> oklog/syslog  2.016s
> okmath0.003s
> okmath/big0.397s
> okmath/cmplx  0.014s
> okmath/rand   0.088s
> okmime0.014s
> okmime/multipart  0.370s
> okmime/quotedprintable0.156s
> oknet 1.516s
> oknet/http9.628s
> oknet/http/cgi0.240s
> oknet/http/cookiejar  0.005s
> oknet/http/fcgi   0.004s
> oknet/http/httptest   0.013s
> oknet/http/httptrace  0.002s
> oknet/http/httputil   0.021s
> oknet/http/internal   0.002s
> oknet/internal/socktest   0.002s
> oknet/mail

Bug#839298: marked as done (golang-1.6: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 22:37:57 +
with message-id 
and subject line Bug#839298: fixed in golang-1.6 1.6.3-2
has caused the Debian Bug report #839298,
regarding golang-1.6: FTBFS: tests 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.)


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

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> set -ex; \
>   cd src; \
>   export PATH="/<>/bin:$PATH"; \
>   eval "$(go tool dist env)"; \
>   bash run.bash -k -no-rebuild;
> + cd src
> + export 
> PATH=/<>/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> + go tool dist env
> + eval CC="gcc"
> CC_FOR_TARGET="gcc"
> GOROOT="/<>"
> GOBIN="/<>/bin"
> GOARCH="amd64"
> GOOS="linux"
> GOHOSTARCH="amd64"
> GOHOSTOS="linux"
> GOTOOLDIR="/<>/pkg/tool/linux_amd64"
> + CC=gcc
> + CC_FOR_TARGET=gcc
> + GOROOT=/<>
> + GOBIN=/<>/bin
> + GOARCH=amd64
> + GOOS=linux
> + GOHOSTARCH=amd64
> + GOHOSTOS=linux
> + GOTOOLDIR=/<>/pkg/tool/linux_amd64
> + bash run.bash -k -no-rebuild
> 
> # Testing packages.
> okarchive/tar 0.022s
> okarchive/zip 0.077s
> okbufio   0.090s
> okbytes   0.125s
> okcompress/bzip2  0.111s
> okcompress/flate  0.250s
> okcompress/gzip   0.033s
> okcompress/lzw0.006s
> okcompress/zlib   0.025s
> okcontainer/heap  0.014s
> okcontainer/list  0.016s
> okcontainer/ring  0.016s
> okcrypto/aes  0.034s
> okcrypto/cipher   0.004s
> okcrypto/des  0.014s
> okcrypto/dsa  0.007s
> okcrypto/ecdsa0.048s
> okcrypto/elliptic 0.048s
> okcrypto/hmac 0.003s
> okcrypto/md5  0.004s
> okcrypto/rand 0.039s
> okcrypto/rc4  0.143s
> okcrypto/rsa  0.153s
> okcrypto/sha1 0.012s
> okcrypto/sha256   0.013s
> okcrypto/sha512   0.007s
> okcrypto/subtle   0.011s
> okcrypto/tls  1.367s
> okcrypto/x509 1.439s
> okdatabase/sql0.071s
> okdatabase/sql/driver 0.002s
> okdebug/dwarf 0.014s
> okdebug/elf   0.024s
> okdebug/gosym 0.281s
> okdebug/macho 0.021s
> okdebug/pe0.020s
> okdebug/plan9obj  0.005s
> okencoding/ascii850.009s
> okencoding/asn1   0.008s
> okencoding/base32 0.004s
> okencoding/base64 0.003s
> okencoding/binary 0.012s
> okencoding/csv0.014s
> okencoding/gob0.045s
> okencoding/hex0.013s
> okencoding/json   0.217s
> okencoding/pem0.016s
> okencoding/xml0.030s
> okerrors  0.009s
> okexpvar  0.016s
> okflag0.003s
> okfmt 0.192s
> okgo/ast  0.006s
> okgo/build0.095s
> okgo/constant 0.004s
> okgo/doc  0.041s
> okgo/format   0.012s
> okgo/internal/gccgoimporter   0.003s
> okgo/internal/gcimporter  0.218s
> okgo/parser   0.042s
> okgo/printer  0.496s
> okgo/scanner  0.004s
> okgo/token0.027s
> okgo/types0.794s
> okhash/adler320.006s
> okhash/crc32  0.012s
> okhash/crc64  0.002s
> okhash/fnv0.002s
> okhtml0.004s
> okhtml/template   0.047s
> okimage   0.194s
> okimage/color 0.108s
> okimage/draw  0.108s
> okimage/gif   0.103s
> okimage/jpeg  0.230s
> okimage/png   0.080s
> okindex/suffixarray   0.010s
> okinternal/golang.org/x/net/http2/hpack   0.019s
> okinternal/singleflight   0.013s
> okinternal/trace  0.014s
> okio  0.022s
> okio/ioutil   0.003s
> oklog 0.007s
> oklog/syslog  2.020s
> okmath0.003s
> okmath/big0.565s
> okmath/cmplx  0.015s
> okmath/rand   0.098s
> okmime0.019s
> okmime/multipart  0.597s
> okmime/quotedprintable0.209s
> oknet 1.618s
> oknet/http10.019s
> oknet/http/cgi0.285s
> oknet/http/cookiejar  0.005s
> oknet/http/fcgi   0.004s
> oknet/http/httptest   0.014s
> oknet/http/httputil   0.019s
> oknet/http/internal   0.002s
> oknet/internal/socktest   0.002s
> oknet/mail0.003s
> 

Bug#839364: golang: FTBFS: Go version is "go1.6.1", ignoring -next /<>/api/next.txt

[Tianon Gravi]

On 1 October 2016 at 01:49, Lucas Nussbaum  wrote:
> Source: golang
> Version: 2:1.6.1-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160930 qa-ftbfs
> Justification: FTBFS on amd64

I'm honestly confused about where this one is coming from. :(

The current version of src:golang in both sid and stretch is 2:1.7~1,
and the contents of it are simple metapackages which shouldn't have
any difficulty building.  Is there some cruft in the archive we need
to ask the FTP team to take care of that's causing this older version
to get included in the rebuild?

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Processed: tagging 826192

[Debian Bug Tracking System]

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

> tags 826192 + pending
Bug #826192 [libmath-gsl-perl] libmath-gsl-perl: FTBFS with GSL 2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#839294: rawdog: FTBFS: Tests failures

[Adam Sampson]

Hi Lucas,

On Sat, Oct 01, 2016 at 10:45:00AM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64. [...]
>> expected testauto/output.html to contain 'expand(char())'

Thanks for reporting this. After a bit of digging, I've found that it's
caused by a non-backwards-compatible change in libtidy (which rawdog
uses via the python-libtidy bindings): in libtidy 0.99, the input and
output encodings defaulted to ASCII, whereas libtidy 5 defaults them to
UTF-8. The result is that libtidy takes the HTML that rawdog has already
converted to ASCII, and expands the character references into UTF-8
characters.

On jessie, with libtidy-0.99.0 20091223cvs-1.4+deb8u1:
$ python -c 'import tidylib; print repr(tidylib.tidy_document("", 
{"numeric_entities": 1, "output_html": 1})[0])'
'\n  \n\n  \n  \n\n  
\n\n'

On sid, with libtidy5 5.2.0-2:
$ python -c 'import tidylib; print repr(tidylib.tidy_document("", 
{"numeric_entities": 1, "output_html": 1})[0])'
'\n\n  \n
\n  \n  \n\xc3\x88\n  \n\n'

Specifying the input and output encodings explicitly as ASCII fixes
this. I've made the following change in upstream rawdog, and it'll be
fixed in rawdog 2.22:

diff --git a/rawdoglib/rawdog.py b/rawdoglib/rawdog.py
index d1d4e4c..8a6702a 100644
--- a/rawdoglib/rawdog.py
+++ b/rawdoglib/rawdog.py
@@ -136,6 +136,8 @@ def sanitise_html(html, baseurl, inline, config):
if config["tidyhtml"]:
args = {
"numeric_entities": 1,
+   "input_encoding": "ascii",
+   "output_encoding": "ascii",
"output_html": 1,
"output_xhtml": 0,
"output_xml": 0,

Cheers,

-- 
Adam Sampson  

Bug#839010: marked as done (bind9: CVE-2016-2776: Assertion failure in query processing)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 22:03:06 +
with message-id 
and subject line Bug#839010: fixed in bind9 1:9.9.5.dfsg-9+deb8u7
has caused the Debian Bug report #839010,
regarding bind9: CVE-2016-2776: Assertion failure in query processing
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.)


-- 
839010: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Version: 1:9.10.3.dfsg.P4-10.1
Tags: security
Severity: grave

ISC has released a security alert at

  

Relevant information from this report follows:

CVE:   CVE-2016-2776
Document Version:  2.0
Posting date:  2016-09-27
Program Impacted:  BIND
Versions affected: 9.0.x -> 9.8.x, 9.9.0->9.9.9-P2, 9.9.3-S1->9.9.9-S3,
   9.10.0->9.10.4-P2, 9.11.0a1->9.11.0rc1
Severity:  High
Exploitable:   Remotely

Description:

   Testing by ISC has uncovered a critical error condition which
   can occur when a nameserver is constructing a response.  A defect
   in the rendering of messages into packets can cause named to
   exit with an assertion failure in buffer.c while constructing a
   response to a query that meets certain criteria.

   This assertion can be triggered even if the apparent source
   address isn't allowed to make queries (i.e. doesn't match
   'allow-query').

Impact:

   All servers are vulnerable if they can receive request packets from
any source.
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.9.5.dfsg-9+deb8u7

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

Debian distribution maintenance software
pp.
Florian Weimer  (supplier of updated bind9 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 27 Sep 2016 19:46:00 +0200
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-90 
libdns100 libisc95 liblwres90 libisccc90 libisccfg90 dnsutils lwresd 
libbind-export-dev libdns-export100 libdns-export100-udeb libisc-export95 
libisc-export95-udeb libisccfg-export90 libisccfg-export90-udeb libirs-export91 
libirs-export91-udeb
Architecture: source all amd64
Version: 1:9.9.5.dfsg-9+deb8u7
Distribution: jessie-security
Urgency: high
Maintainer: LaMont Jones 
Changed-By: Florian Weimer 
Description:
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-90 - BIND9 Shared Library used by BIND
 libdns-export100 - Exported DNS Shared Library
 libdns-export100-udeb - Exported DNS library for debian-installer (udeb)
 libdns100  - DNS Shared Library used by BIND
 libirs-export91 - Exported IRS Shared Library
 libirs-export91-udeb - Exported IRS library for debian-installer (udeb)
 libisc-export95 - Exported ISC Shared Library
 libisc-export95-udeb - Exported ISC library for debian-installer (udeb)
 libisc95   - ISC Shared Library used by BIND
 libisccc90 - Command Channel Library used by BIND
 libisccfg-export90 - Exported ISC CFG Shared Library
 libisccfg-export90-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg90 - Config File Handling Library used by BIND
 liblwres90 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Closes: 831796 839010
Changes:
 bind9 (1:9.9.5.dfsg-9+deb8u7) jessie-security; urgency=high
 .
   * CVE-2016-2775: lwresd crash with long query name.
 Backport of upstream commit 38cc2d14e218e536e0102fa70deef99461354232.
 Closes: #831796.
   * CVE-2016-2776: assertion failure due to unspecified crafted query.
 Fix based on 

Bug#836505: marked as done (elog: CVE-2016-6342: posting entry as arbitrary username by improper authentication)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 22:03:36 +
with message-id 
and subject line Bug#836505: fixed in elog 2.9.2+2014.05.11git44800a7-2+deb8u1
has caused the Debian Bug report #836505,
regarding elog: CVE-2016-6342: posting entry as arbitrary username by improper 
authentication
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.)


-- 
836505: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: elog
Version: 2.9.2+2014.05.11git44800a7-2
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for elog.

CVE-2016-6342[0]:
posting entry as arbitrary username by improper authentication

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-6342

Using severity grave, since for at least stretch this should be fixed
to be in a fixed version. I OTOH do not know elog well enough to see
if the affected setup is actual a frequent one.

Could you as well schedule a fix for the stable version via a
point-release, cf.
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#upload-stable

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: elog
Source-Version: 2.9.2+2014.05.11git44800a7-2+deb8u1

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

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

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

Debian distribution maintenance software
pp.
Roger Kalt  (supplier of updated elog package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Sep 2016 20:22:36 +0200
Source: elog
Binary: elog
Architecture: source amd64
Version: 2.9.2+2014.05.11git44800a7-2+deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Roger Kalt 
Changed-By: Roger Kalt 
Description:
 elog   - Logbook system to manage notes through a Web interface
Closes: 836505
Changes:
 elog (2.9.2+2014.05.11git44800a7-2+deb8u1) jessie; urgency=medium
 .
   * Added patch 0005_elogd_CVE-2016-6342_fix to fix posting entry as
 arbitrary username (Closes: #836505, CVE-2016-6342)
Checksums-Sha1:
 157b7e960df3e269bee4eb925aeadd70fd0e3d5f 1855 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1.dsc
 c330b954e4bc5f6181c3a7f707b9f8acd402cf44 20160 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1.debian.tar.xz
 12b3cfe5a0b7b1e338250a83425135fae28f4686 1299088 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1_amd64.deb
Checksums-Sha256:
 91962ae6acf8321e0b3b52cff0def990b3aec4983fa5e59d9cfb8b911a4dbf84 1855 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1.dsc
 698fb4e2513acb71a2721b52cd174368ebb29f87a7d4d2d4a77a70566c041ea5 20160 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1.debian.tar.xz
 8dc1b4543a9224815de08a9fa3f90910baed4ed5223dfe62f440cd9eafd37d66 1299088 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1_amd64.deb
Files:
 af64171ed8008b57ea7be91df84dbd46 1855 web optional 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1.dsc
 847fee445bfd1074dd1b36151eda8ef0 20160 web optional 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1.debian.tar.xz
 f96cc48d04aee014d55b3f34dad15fe7 1299088 web optional 
elog_2.9.2+2014.05.11git44800a7-2+deb8u1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX8YyxAAoJEC/5zVlhJha1U10QAI8Bff6btCIhKA4EjZv+qk1n
TsNr5xELN9IrjYh5S+A1y3iKgkWpNWqLyYzF0L9t4DIpS5M6oT/sMEeP2sHrVdtU
1euPssZEBLxZu1qOY49j+Km8e9EBxsTf+2kV5wqkUX6pIgDpUqJjLxcTu8S6aTtm
7ypQ680uH9DMsxwNWNn+/n9ldPkdK9siCvYUJRN3KAAiMI8/yIHlLVOdXFEixIbs
1Pe34vqZEliKEAbKq8Mfxtd4unP6AEmHJyZLVhj6gHD380L4sk00ePEHZmjkQB8M
G9w41tU16AS+1DGM5kEHxOqiD4ZOIonno97akfUFSxGVVVo4ePnegoe5OghFxiJl
eLw5+O74qcrddYdiq4UmkisKhqx0AXRuxQveDifNc9nJ7ED3KmnmMUIbHf+ziFAs
OfLH4mPs3qp11MqT4fVM+CTrRM57eCc981uOC82LAi7DN3wmal5ywtj70Z4vtFO+
lozna9k7f8qNSZeZfKMsr/oGwEK50OnGxRov+Ccf2CgZtUEzs6U/9+kVczaifY8j
dM87Ul8+rlUhpzA3qMVDH+KOT85K/RLy9t58M7fjFP/5oV3iJSFFmOegYYjyCgli

Bug#837714: marked as done (libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero data size file overwrite)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 22:03:37 +
with message-id 
and subject line Bug#837714: fixed in libarchive 3.1.2-11+deb8u3
has caused the Debian Bug report #837714,
regarding libarchive: CVE-2016-5418: Archive Entry with type 1 (hardlink), but 
has a non-zero data size file overwrite
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.)


-- 
837714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libarchive
Version: 3.2.1-2
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for libarchive.

CVE-2016-5418[0]:
|Archive Entry with type 1 (hardlink), but has a non-zero data size
|file overwrite

This corresponds to [1] and [2], which is upstream as [3].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-5418
[1] 
https://git.centos.org/blob/rpms!libarchive.git/9952851f8b327a8c93d26a5873c190c1fb09ae6c/SOURCES!libarchive-3.1.2-CVE-2016-5418.patch;jsessionid=1dexz8h9qdewibih5aonbu3
[2] 
https://git.centos.org/blob/rpms!libarchive.git/9952851f8b327a8c93d26a5873c190c1fb09ae6c/SOURCES!libarchive-3.1.2-CVE-2016-5418-variation.patch;jsessionid=1dexz8h9qdewibih5aonbu3
[3] 
https://github.com/libarchive/libarchive/commit/dfd6b54ce33960e420fb206d8872fb759b577ad9

Please adjust the affected versions in the BTS as needed. jessie
version has not been checked yet, but is probably similar affected.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libarchive
Source-Version: 3.1.2-11+deb8u3

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libarchive 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Sep 2016 13:25:26 +0200
Source: libarchive
Binary: libarchive-dev libarchive13 bsdtar bsdcpio
Architecture: source
Version: 3.1.2-11+deb8u3
Distribution: jessie-security
Urgency: high
Maintainer: Debian Libarchive Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 837714
Description: 
 bsdcpio- Implementation of the 'cpio' program from FreeBSD
 bsdtar - Implementation of the 'tar' program from FreeBSD
 libarchive-dev - Multi-format archive and compression library (development 
files)
 libarchive13 - Multi-format archive and compression library (shared library)
Changes:
 libarchive (3.1.2-11+deb8u3) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2016-7166: Denial of service using a crafted gzip file
   * CVE-2016-6250: Integer overflow in the ISO9660 writer
   * CVE-2016-5418: Archive Entry with type 1 (hardlink), but has a non-zero
 data size file overwrite (Closes: #837714)
Checksums-Sha1: 
 effe9337181e17f0dbedd313ec796cb59dd66cba 2453 libarchive_3.1.2-11+deb8u3.dsc
 518986a94568b2111a1e087a0ca0cd5ebaa9b268 36064 
libarchive_3.1.2-11+deb8u3.debian.tar.xz
Checksums-Sha256: 
 5838e99469280cb3e90653d327c5b3b315fba810414591cb45206488017fb598 2453 
libarchive_3.1.2-11+deb8u3.dsc
 ab2c0220d1253675b07a23c6fe8a4eeea9d59168b165bdf59f6a93c78d25fbe0 36064 
libarchive_3.1.2-11+deb8u3.debian.tar.xz
Files: 
 3345cb4ec3faea86a57c70d9fffd703e 2453 libs optional 
libarchive_3.1.2-11+deb8u3.dsc
 10b2951cb6feb392bb6d3831797982e2 36064 libs optional 
libarchive_3.1.2-11+deb8u3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKPBAEBCgB5BQJX54P9XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NjQ0NDA5ODA4QzE3MUUwNTUzMURERUUw
NTRDQjhGMzEzNDNDRjQ0EhxjYXJuaWxAZGViaWFuLm9yZwAKCRAFTLjzE0PPRDHE
EACMnMrIj3TPAhWfJ0azDLuFkU7xWZWwaSHGAN87cZ6OjRTg8I3U0VLkpXrATpFA
LXrog/M/ahyM3y4obPNroVUbYwz0tk0Yh/UPa9szVKOPfcprJUyW9iXX0u3oP6Zo

Bug#838248: marked as done (unadf: CVE-2016-1243 and CVE-2016-1244)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 22:03:46 +
with message-id 
and subject line Bug#838248: fixed in unadf 0.7.11a-3+deb8u1
has caused the Debian Bug report #838248,
regarding unadf: CVE-2016-1243 and CVE-2016-1244
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.)


-- 
838248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unadf
Version: 0.7.11a-3
Severity: important
Tags: security patch

Hi,

Tuomas Räsänen discovered the following vulnerabilities for unadf.

CVE-2016-1243[0]: stack buffer overflow caused by blindly trusting on pathname 
lengths of archived files.
CVE-2016-1244[1]: execution of unsanitized input

The patch is available here: 
  
http://tmp.tjjr.fi/0001-Fix-unsafe-extraction-by-using-mkdir-instead-of-shel.patch

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-1243
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1243
[1] https://security-tracker.debian.org/tracker/CVE-2016-1244
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1244
--- End Message ---
--- Begin Message ---
Source: unadf
Source-Version: 0.7.11a-3+deb8u1

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

Debian distribution maintenance software
pp.
Luciano Bello  (supplier of updated unadf 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: Sun, 18 Sep 2016 23:11:18 -0400
Source: unadf
Binary: unadf
Architecture: source amd64
Version: 0.7.11a-3+deb8u1
Distribution: stable-security
Urgency: high
Maintainer: Debian QA Group 
Changed-By: Luciano Bello 
Description:
 unadf  - Extract files from an Amiga Disk File dump (.adf)
Closes: 838248
Changes:
 unadf (0.7.11a-3+deb8u1) stable-security; urgency=high
 .
   * Orphaned package with security issues.
   * Tuomas Räsäne discoveried two security issues (Closes: #838248):
 - CVE-2016-1243: stack buffer overflow caused by blindly trusting on
 pathname lengths of archived files.
 - CVE-2016-1244: execution of unsanitized input.
Checksums-Sha1:
 a9833a042a8124bfdbe6c305b79b63a419258c96 1723 unadf_0.7.11a-3+deb8u1.dsc
 63c05f97302ff67f5d7ff2d9e33f9a66196f9578 209458 unadf_0.7.11a.orig.tar.gz
 d7a189f0824ddc05cbe13dde8ba7280bc0c2ae91 19368 
unadf_0.7.11a-3+deb8u1.debian.tar.xz
 330193a8f503a1666a6294c0bec3c52b298c8f7e 22 
unadf_0.7.11a-3+deb8u1_amd64.deb
Checksums-Sha256:
 cdf0531de6b73dfe4ab7f4d9a0886ae4b2565d4f5f5a48fb1db3bf0953c1319b 1723 
unadf_0.7.11a-3+deb8u1.dsc
 fa9e0e34b1b0f4f4287905a3d485e3bba498451af98d6c12be87ab3a2b436471 209458 
unadf_0.7.11a.orig.tar.gz
 6aa90a89df12f712098d62213eb35c2d4195bfbea389af4936d8a74f6f6b78bc 19368 
unadf_0.7.11a-3+deb8u1.debian.tar.xz
 a30718e98459f6c3b2d292cdf67115dba3f77c26b6e5530c1b244daec20d018d 22 
unadf_0.7.11a-3+deb8u1_amd64.deb
Files:
 09671a48add8e2d1998572c1f28fd258 1723 utils optional unadf_0.7.11a-3+deb8u1.dsc
 63c21eeb61e1473d8dd214e0b39cb819 209458 utils optional 
unadf_0.7.11a.orig.tar.gz
 01bc54dc8cce49609bf509dfd6182ded 19368 utils optional 
unadf_0.7.11a-3+deb8u1.debian.tar.xz
 388dd0e716d5bb36096a1217609b38dd 22 utils optional 
unadf_0.7.11a-3+deb8u1_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJX5shEAAoJEG7C3vaP/jd0VVMQAI3I7PjzwtpBxz8iGaIYCkHq
1JwEQGcO8QsEdekVfb8aWVan2xOIBw0rfgA3HHa8l8EwA6EInAdNOBhF/TxwMo5P
5myXhOyMj5LBsgT+7V4BRaoH9wM4TEP/K6EW5hpd1RHiZWdUni2B0zijelz8pzcf
VtwiVIZCkdblWIjqnxeeU1rQNvUBXkVU1/EDOZlg/ePzySQSXFDFT5JVkbbPGAVW
EMIJC6j5GeN06bFi6fN7wZlK3kVTzmrgBNQZitMHuMC9Cjdah5RzPmh/vyU6Za+v
alzvkLDNdn6R4J2sgtf3Eg5ol6FNjGKZDIbd5PfI/q3KWj1R+wWA/01DRur3yP+Y
c+cQi+4SpXlXOYYSnOC2x9qJvAt47T5lXfaPXQ2q00wPckch3nUegxn0qCUExS+U
Bnx+6fngdqVdCQGmJjo4qEcDQEdhUFEYURis0E3VLQP8afk+slu8xaFeWAS2APMg

Bug#830748: supertuxkart: FTBFS on arm64, mips/mips64/mipsel, ppc64el, s390x

[Deve]

Hi,

It should be fixed in this commit:
https://github.com/supertuxkart/stk-code/commit/5e05f1178ce6bc5f3a653b55ab3dc6d016196341

This modification is already applied in upstream angelscript:
https://sourceforge.net/p/angelscript/code/2353/

Vincent Cheng confirmed that it works in this comment:
https://github.com/supertuxkart/stk-code/issues/2569#issuecomment-250677264

I attached the patch.

Regards,
Deve
>From 5e05f1178ce6bc5f3a653b55ab3dc6d016196341 Mon Sep 17 00:00:00 2001
From: Deve 
Date: Mon, 3 Oct 2016 23:26:09 +0200
Subject: [PATCH] Fixed compiler error on Linux with non-x86 64bit platforms,
 e.g. arm64, mips, and s390x architectures

This modification is already applied in upstream angelscript repository:
https://sourceforge.net/p/angelscript/code/2353/

Thanks to Adrian Bunk and Andreas Jonsson
---
 lib/angelscript/projects/cmake/CMakeLists.txt | 1 +
 lib/angelscript/source/as_config.h| 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)

diff --git a/lib/angelscript/projects/cmake/CMakeLists.txt b/lib/angelscript/projects/cmake/CMakeLists.txt
index e939713..755d837 100644
--- a/lib/angelscript/projects/cmake/CMakeLists.txt
+++ b/lib/angelscript/projects/cmake/CMakeLists.txt
@@ -67,6 +67,7 @@ set(ANGELSCRIPT_SOURCE
 ../../source/as_builder.cpp
 ../../source/as_bytecode.cpp
 ../../source/as_callfunc.cpp
+../../source/as_callfunc_mips.cpp
 ../../source/as_callfunc_x86.cpp
 ../../source/as_callfunc_x64_gcc.cpp
 ../../source/as_callfunc_x64_msvc.cpp
diff --git a/lib/angelscript/source/as_config.h b/lib/angelscript/source/as_config.h
index cb05bff..5bb5b8e 100644
--- a/lib/angelscript/source/as_config.h
+++ b/lib/angelscript/source/as_config.h
@@ -844,7 +844,7 @@
 			#define THISCALL_PASS_OBJECT_POINTER_ON_THE_STACK
 			#define AS_X86
 			#undef AS_NO_THISCALL_FUNCTOR_METHOD
-		#elif defined(__LP64__) && !defined(__arm64__)
+		#elif defined(__x86_64__)
 			#define AS_X64_GCC
 			#undef AS_NO_THISCALL_FUNCTOR_METHOD
 			#define HAS_128_BIT_PRIMITIVES
-- 
2.7.4

Bug#839686: forked-daapd: does not recreate stuff in /var/cache after deletion

[Dominik George]

Package: forked-daapd
Version: 24.1-1+b1
Severity: serious
Justification: Policy 9.1.1

After deleting /var/cache/forked-daapd, forked-daapd cannot start up
again because it fails to open the database.

forked-daapd seems to require its data files there, while the FHS
unmistakably states:

"Unlike /var/spool, the cached files can be deleted without data loss.
The data must remain valid between invocations of the application and
rebooting the system.

Files located under /var/cache may be expired in an application specific
manner, by the system administrator, or both. The application must
always be able to recover from manual deletion of these files (generally
because of a disk space shortage). No other requirements are made on the
data format of the cache directories."

Please note that while the below information states this is Raspbian, I
can assure that forked-daapd and all its dependencies on this system are
plain Debian armhf ☺.

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

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

Versions of packages forked-daapd depends on:
ii  adduser 3.115
ii  avahi-daemon0.6.32-1
ii  libantlr3c-3.2-03.2-3
ii  libasound2  1.1.2-1
ii  libavahi-client30.6.32-1
ii  libavahi-common30.6.32-1
ii  libavcodec-extra57  7:3.1.3-1+b3
ii  libavfilter67:3.1.3-1+b3
ii  libavformat57   7:3.1.3-1+b3
ii  libavutil55 7:3.1.3-1+b3
ii  libc6   2.24-3
ii  libconfuse1 3.0+dfsg-2
ii  libcurl3-gnutls 7.50.1-1
ii  libevent-2.0-5  2.0.21-stable-2+b1
ii  libgcrypt20 1.7.3-1
ii  libgnutls30 3.5.4-2
ii  libgpg-error0   1.24-1
ii  libjson-c3  0.12.1-1
ii  libmxml12.10-1
ii  libplist3   1.12-3.1
ii  libprotobuf-c1  1.2.1-1+b1
ii  libsqlite3-03.14.2-1
ii  libswscale4 7:3.1.3-1+b3
ii  libunistring0   0.9.6+really0.9.3-0.1
ii  psmisc  22.21-2.1
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages forked-daapd recommends:
ii  libavcodec-extra   7:3.1.3-1
ii  libavcodec-extra57 [libavcodec-extra]  7:3.1.3-1+b3

forked-daapd suggests no packages.

-- Configuration Files:
/etc/forked-daapd.conf changed [not included]

-- no debconf information

Bug#839567: rake does not work with jruby

[Helmut Grohne]

On Mon, Oct 03, 2016 at 11:13:13AM +0200, Emmanuel Bourg wrote:
> What is the expected contract for a package providing ruby-interpreter?

I wish I could tell. Judging from
https://wiki.debian.org/Teams/Ruby/Packaging, it seems that
ruby-interpreter requires /usr/bin/ruby. Not sure how official that is.

> Do it just have to offer a /usr/bin/ruby alternative?

As soon as /usr/bin/ruby becomes managed by update-alternatives or
dpkg-divert, ruby itself must drop Multi-Arch: allowed, because it no
longer is in exclusive control of /usr/bin/ruby. So this sounds wrong.

I'm not sure we currently support non-default ruby implementations.
Which indicates that jruby should simply drop the provides.

Not speaking with any ruby hats. Maybe Christian can weigh in with more
details.

Helmut

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 831085 2.1-1.1
Bug #831085 [src:socnetv] socnetv: FTBFS with GCC 6: cstdlib:75:25: fatal 
error: stdlib.h: No such file or directory
Marked as fixed in versions socnetv/2.1-1.1.
>
End of message, stopping processing here.

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

Processed: tagging 831114

[Debian Bug Tracking System]

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

> # fixed in latest upstream release
> tags 831114 + pending
Bug #831114 {Done: Daniel Leidert } [src:travis] travis: 
FTBFS with GCC 6: stl_algobase.h:265:56: error: macro "max" passed 3 arguments, 
but takes just 2
Ignoring request to alter tags of bug #831114 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: Raise the severity

[Debian Bug Tracking System]

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

> severity 839603 grave
Bug #839603 [amanda-server] amanda: The /usr/lib/amanda/amcheck-device command 
SIGSEGV when called by amcheck
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: tagging 831114

[Debian Bug Tracking System]

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

> # fixed in latest upstream release
> tags 831114 + pending
Bug #831114 {Done: Daniel Leidert } [src:travis] travis: 
FTBFS with GCC 6: stl_algobase.h:265:56: error: macro "max" passed 3 arguments, 
but takes just 2
Ignoring request to alter tags of bug #831114 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#839190: marked as done (wordpress 4.1+dfsg-1+deb8u10 regression)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 19:17:08 +
with message-id 
and subject line Bug#839190: fixed in wordpress 4.1+dfsg-1+deb8u11
has caused the Debian Bug report #839190,
regarding wordpress 4.1+dfsg-1+deb8u10 regression
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.)


-- 
839190: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wordpress
Version: 4.1+dfsg-1+deb8u10
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I've just applied a normal update to jessie, and wordpress 4.1+dfsg-1+deb8u10
(security fix) exhibits a regression, which causes all wordpress sites to fail
with the following error in the web server error log:

Thu Sep 29 23:56:10 2016 - PHP Fatal error:  Cannot redeclare wp_json_encode() \
(previously declared in /usr/share/wordpress/wp-includes/functions.php:2649) \
in /usr/share/wordpress/wp-includes/functions.php on line 2818

Downgrading to 4.1+dfsg-1+deb8u9 restores expected behaviour.

Cheers,
Phil.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wordpress depends on:
ii  ca-certificates  20141019+deb8u1
ii  libjs-cropper1.2.2-1
ii  libjs-mediaelement   2.15.1+dfsg-1
ii  libphp-phpmailer 5.2.9+dfsg-2+deb8u1
ii  mysql-client-5.5 [mysql-client]  5.5.52-0+deb8u1
ii  nginx-full [httpd]   1.6.2-5+deb8u2+b1
ii  php-getid3   1.9.8-3
ii  php5 5.6.24+dfsg-0+deb8u1
ii  php5-gd  5.6.24+dfsg-0+deb8u1
ii  php5-mysql   5.6.24+dfsg-0+deb8u1
ii  wordpress-theme-twentyfifteen4.1+dfsg-1+deb8u10

Versions of packages wordpress recommends:
ii  wordpress-l10n  4.1+dfsg-1+deb8u10

Versions of packages wordpress suggests:
ii  mysql-server  5.5.52-0+deb8u1
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 4.1+dfsg-1+deb8u11

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

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

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated wordpress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 01 Oct 2016 11:38:14 +0200
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentyfifteen 
wordpress-theme-twentyfourteen wordpress-theme-twentythirteen
Architecture: source all
Version: 4.1+dfsg-1+deb8u11
Distribution: jessie-security
Urgency: high
Maintainer: Craig Small 
Changed-By: Yves-Alexis Perez 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files
 wordpress-theme-twentyfourteen - weblog manager - twentyfourteen theme files
 wordpress-theme-twentythirteen - weblog manager - twentythirteen theme files
Closes: 839190
Changes:
 wordpress (4.1+dfsg-1+deb8u11) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * debian/patches/CVE-2016-6635.patch:
 - don't duplicate wp_encode_json() which has already been backported
   upstream, just merge later changes, fix regression in the previous
   upload.   closes: #839190
   * debian/languages: fix language with "\n" inconsistencies in msgid/msgstr.
Checksums-Sha1:
 760d8f442093f2980779e6cc14e6fdd8d486dfb8 2173 wordpress_4.1+dfsg-1+deb8u11.dsc
 017ed5af867e0028c790544842801944fb2cb069 6031528 
wordpress_4.1+dfsg-1+deb8u11.debian.tar.xz
 d8742e21b7b20ef883ed9a7023e490e8a067e8a8 3170566 
wordpress_4.1+dfsg-1+deb8u11_all.deb
 ba9e22494977653906d1d9aa27b78eb622e7f6f3 4073284 

Bug#839475: marked as done (lttnganalyses: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 19:19:34 +
with message-id 
and subject line Bug#839475: fixed in lttnganalyses 0.5.4-2
has caused the Debian Bug report #839475,
regarding lttnganalyses: FTBFS: dh_auto_test: pybuild --test -i python{version} 
-p 3.5 returned exit code 13
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses
> copying lttnganalyses/_version.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses
> copying lttnganalyses/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses
> creating /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/common
> copying lttnganalyses/common/version_utils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/common
> copying lttnganalyses/common/parse_utils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/common
> copying lttnganalyses/common/format_utils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/common
> copying lttnganalyses/common/time_utils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/common
> copying lttnganalyses/common/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/common
> copying lttnganalyses/common/trace_utils.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/common
> creating /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/io.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/stats.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/irq.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/syscalls.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/sched.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/cputop.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/analysis.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> copying lttnganalyses/core/memtop.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/core
> creating /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/io.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/irq.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/termgraph.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/command.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/mi.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/syscallstats.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/sched.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/cputop.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/progressbar.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> copying lttnganalyses/cli/memtop.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/cli
> creating 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/linuxautomaton
> copying lttnganalyses/linuxautomaton/net.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/linuxautomaton
> copying lttnganalyses/linuxautomaton/io.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/lttnganalyses/linuxautomaton
> copying lttnganalyses/linuxautomaton/block.py -> 
> 

Bug#806616: marked as done (fftw3: FTBFS when built with dpkg-buildpackage -A (build-indep fails))

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 19:19:07 +
with message-id 
and subject line Bug#806616: fixed in fftw3 3.3.5-1
has caused the Debian Bug report #806616,
regarding fftw3: FTBFS when built with dpkg-buildpackage -A (build-indep fails)
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.)


-- 
806616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fftw3
Version: 3.3.4-2
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
(cd doc ; /usr/bin/make -j1 -k clean)
make[1]: Entering directory '/<>/doc'
make[1]: *** No rule to make target 'clean'.
make[1]: Leaving directory '/<>/doc'
debian/rules:104: recipe for target 'build-indep' failed
make: [build-indep] Error 2 (ignored)
rm -f doc/*.info* doc/rfftwnd.png doc/html/*
cd doc/FAQ && /usr/bin/make -j1 fftw-faq.html fftw-faq.ascii
make[1]: Entering directory '/<>/doc/FAQ'
make[1]: Nothing to be done for 'fftw-faq.html'.
make[1]: Nothing to be done for 'fftw-faq.ascii'.
make[1]: Leaving directory '/<>/doc/FAQ'
cd doc && /usr/bin/make -j1 && /usr/bin/make -j1 html
make[1]: Entering directory '/<>/doc'
make[1]: *** No targets specified and no makefile found.  Stop.
make[1]: Leaving directory '/<>/doc'
debian/rules:104: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.
--- End Message ---
--- Begin Message ---
Source: fftw3
Source-Version: 3.3.5-1

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

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated fftw3 
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: Mon, 03 Oct 2016 18:12:31 +0200
Source: fftw3
Binary: libfftw3-3 libfftw3-single3 libfftw3-double3 libfftw3-long3 
libfftw3-quad3 libfftw3-bin libfftw3-mpi3 libfftw3-dev libfftw3-mpi-dev 
libfftw3-doc libfftw3-dbg
Architecture: source amd64 all
Version: 3.3.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Ghislain Antony Vaillant 
Description:
 libfftw3-3 - Library for computing Fast Fourier Transforms
 libfftw3-bin - Library for computing Fast Fourier Transforms - Tools
 libfftw3-dbg - Library for computing Fast Fourier Transforms - debug symbols
 libfftw3-dev - Library for computing Fast Fourier Transforms - development
 libfftw3-doc - Documentation for fftw version 3
 libfftw3-double3 - Library for computing Fast Fourier Transforms - Double 
precision
 libfftw3-long3 - Library for computing Fast Fourier Transforms - Long precision
 libfftw3-mpi-dev - MPI Library for computing Fast Fourier Transforms - 
development
 libfftw3-mpi3 - MPI Library for computing Fast Fourier Transforms
 libfftw3-quad3 - Library for computing Fast Fourier Transforms - Quad precision
 libfftw3-single3 - Library for computing Fast Fourier Transforms - Single 
precision
Closes: 806616
Changes:
 fftw3 (3.3.5-1) unstable; 

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

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 19:17:07 +
with message-id 
and subject line Bug#837090: fixed in wordpress 4.1+dfsg-1+deb8u10
has caused the Debian Bug report #837090,
regarding wordpress: CVE-2016-6896 CVE-2016-6897
to be marked as done.

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

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


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

Hi,

the following vulnerabilities were published for wordpress.

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

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

For further information see:

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

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

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

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 10 Sep 2016 08:07:11 +1000
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentyfifteen 
wordpress-theme-twentyfourteen wordpress-theme-twentythirteen
Architecture: source all
Version: 4.1+dfsg-1+deb8u10
Distribution: jessie-security
Urgency: high
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files
 wordpress-theme-twentyfourteen - weblog manager - twentyfourteen theme files
 wordpress-theme-twentythirteen - weblog manager - twentythirteen theme files
Closes: 837090
Changes:
 wordpress (4.1+dfsg-1+deb8u10) jessie-security; urgency=high
 .
   * Backport patches from 4.6.1/4.1.13 Closes: #837090
   * CVE-2016-6896 and CVE-2016-6897 not vulnerable
   * Changeset 38538 sanitize filename in media CVE-2016-7168
   * Changeset 38524 sanitize filename upload upgrader  CVE-2016-7169
   * CVE-2016-4029:
 WordPress before 4.5 does not consider octal and hexadecimal IP address
 formats when determining an intranet address, which allows remote attackers
 to bypass an intended SSRF protection mechanism via a crafted address.
   * CVE-2016-6634:
 Cross-site scripting (XSS) vulnerability in the network settings page in
 WordPress before 4.5 allows remote attackers to inject arbitrary web script
 or HTML via unspecified vectors.
   * CVE-2016-6635:
 Cross-site request forgery (CSRF) vulnerability in the
 wp_ajax_wp_compression_test function in wp-admin/includes/ajax-actions.php
 in WordPress before 4.5 allows remote attackers to hijack the
 authentication of administrators for requests that change the script
 compression option.
Checksums-Sha1:
 f092fb1eb33a47380c0ec8ca362c52ebf9906746 2537 wordpress_4.1+dfsg-1+deb8u10.dsc
 ac437190e0ea392da4ccc5262ef9233c35166ae5 6126040 
wordpress_4.1+dfsg-1+deb8u10.debian.tar.xz
 184e136386021352b8090b5d25a1460d861e1349 3172420 
wordpress_4.1+dfsg-1+deb8u10_all.deb
 106fa24dea9a667e2fe2f479e87a19331ca87f59 4236622 
wordpress-l10n_4.1+dfsg-1+deb8u10_all.deb
 66e6711ced807d7af8771bcdf3211b099ce64ede 502012 
wordpress-theme-twentyfifteen_4.1+dfsg-1+deb8u10_all.deb
 

Bug#839320: [Debian-med-packaging] Bug#839320: gubbins: FTBFS: Tests failures

[Sascha Steinbiss]

Hi all,

can anyone reproduce the failure as indicated in the bug submitter’s build log? 
My own cowbuilder build (unstable amd64) succeeds at ‘test_change_window_size' 
but fails at ‘test_robinson_foulds_convergence’ (the latter I have checked with 
upstream and they are happy to have this test simply disabled).

Cheers
Sascha


> On 1 Oct 2016, at 10:43, Lucas Nussbaum  wrote:
> 
> Source: gubbins
> Version: 2.1.0-1
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160930 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part (hopefully):
>> 
>> ==
>> ERROR: test_change_window_size 
>> (test_external_dependancies.TestExternalDependancies)
>> --
>> Traceback (most recent call last):
>>  File "/<>/python/gubbins/tests/test_external_dependancies.py", 
>> line 34, in test_change_window_size
>>gubbins_runner.parse_and_run()
>>  File "/<>/python/gubbins/common.py", line 263, in parse_and_run
>>sys.exit("Failed while running RAxML internal sequence reconstruction")
>> SystemExit: Failed while running RAxML internal sequence reconstruction
>> 
>> --
>> Ran 77 tests in 9.197s
>> 
>> FAILED (errors=1)
>> debian/rules:23: recipe for target 'override_dh_auto_test' failed
> 
> If the failure looks somehow time/timezone related:
> Note that this rebuild was performed without the 'tzdata' package
> installed in the chroot. tzdata used be (transitively) part of
> build-essential, but it no longer is. If this package requires it to
> build, it should be added to build-depends. For the release team's
> opinion on this, see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185
> 
> The full build log is available from:
>   http://aws-logs.debian.net/2016/09/30/gubbins_2.1.0-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging

Processed: Re: Bug#835336: influxdb: FTBFS in testing (go generate returned exit code 1)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #835336 [src:influxdb] influxdb: FTBFS in testing (go generate returned 
exit code 1)
Added tag(s) patch.

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

Processed: tagging 831114

[Debian Bug Tracking System]

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

> # fixed in latest upstream release
> tags 831114 + pending
Bug #831114 {Done: Daniel Leidert } [src:travis] travis: 
FTBFS with GCC 6: stl_algobase.h:265:56: error: macro "max" passed 3 arguments, 
but takes just 2
Ignoring request to alter tags of bug #831114 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#835336: influxdb: FTBFS in testing (go generate returned exit code 1)

[Guillem Jover]

Control: tag -1 patch

On Wed, 2016-08-24 at 16:03:09 +0200, Santiago Vila wrote:
> Package: src:influxdb
> Version: 0.13.0+dfsg1-4
> Severity: serious

> I tried to build this package on stretch with dpkg-buildpackage -A and
> sbuild and it failed with an error like this:
> 
> --
> go generate -v -ldflags=-X main.version=0.13.0 github.com/[...]
>  [ very long list, see attach for details] returned exit code 1
> --
> 
> I attach five different build logs on two different virtual machines.
> The builds were made on a virtual machine having either 6GB or 3GB of RAM,
> and 4GB of swap.
> 
> I was able to build version 0.10.2+dfsg1-2 without problems.

This is a problem with the statik generator which seems to be unable
to cope with the generated file existing already. Attached a patch
fixing this issues.

Thanks,
Guillem
diff --git a/debian/rules b/debian/rules
index 1254fe4..779bdd1 100755
--- a/debian/rules
+++ b/debian/rules
@@ -37,6 +37,9 @@ override_dh_auto_configure:
 	cp -v $(SOURCE)/influxql/*.tmpl* _build/src/$(DH_GOPKG)/influxql
 	cp -v $(SOURCE)/influxql/tmpldata _build/src/$(DH_GOPKG)/influxql
 
+	# Remove statik files, latest version cannot cope.
+	rm -f _build/src/github.com/influxdata/influxdb/services/admin/statik/statik.go
+
 # influxdb version
 DEB_VERSION := $(shell dpkg-parsechangelog -l$(DEBIAN_DIR)/changelog --show-field Version)
 DEB_NOEPOCH_VERSION := $(shell echo $(DEB_VERSION) | cut -d: -f2-)

Processed: tagging 831114

[Debian Bug Tracking System]

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

> # fixed in latest upstream release
> tags 831114 + pending
Bug #831114 {Done: Daniel Leidert } [src:travis] travis: 
FTBFS with GCC 6: stl_algobase.h:265:56: error: macro "max" passed 3 arguments, 
but takes just 2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#835729: marked as done (jasperreports: FTBFS: build-dependency not installable: libitext-java (>= 2.1.7-11~))

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 20:14:04 +0200
with message-id <11e658bb45532321d5f0bbf6827ec...@webmail.domeneshop.no>
and subject line Re: jasperreports: FTBFS: build-dependency not installable: 
libitext-java (>= 2.1.7-11~)
has caused the Debian Bug report #835729,
regarding jasperreports: FTBFS: build-dependency not installable: libitext-java 
(>= 2.1.7-11~)
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.)


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

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: ant, libbsh-java, debhelper (>= 9), default-jdk, 
> glassfish-javaee, groovy, libantlr-java, libapache-poi-java, libaxis-java, 
> libbatik-java (>= 1.8), libcastor-core-java, libcastor-xml-java, 
> libcommons-beanutils-java, libcommons-codec-java, 
> libcommons-collections3-java, libcommons-digester-java, libcommons-lang-java, 
> libcommons-logging-java, libecj-java, libgeronimo-jpa-2.0-spec-java, 
> libhibernate3-java, libhttpclient-java, libicu4j-java, libitext-java (>= 
> 2.1.7-11~), libjackson2-annotations-java, libjackson2-core-java, 
> libjackson2-databind-java, libjaxen-java, libjaxp1.3-java, libjcommon-java, 
> libjexcelapi-java, libjfreechart-java, liblucene4.10-java (>= 
> 4.10.4+dfsg-2~), libmaven-javadoc-plugin-java, libmondrian-java (>= 
> 1:3.11.0.1-4~), libolap4j-java, librhino-java, libspring-beans-java, 
> libspring-core-java, libxalan2-java, libxmpcore-java, maven-debian-helper, 
> velocity
> Filtered Build-Depends: ant, libbsh-java, debhelper (>= 9), default-jdk, 
> glassfish-javaee, groovy, libantlr-java, libapache-poi-java, libaxis-java, 
> libbatik-java (>= 1.8), libcastor-core-java, libcastor-xml-java, 
> libcommons-beanutils-java, libcommons-codec-java, 
> libcommons-collections3-java, libcommons-digester-java, libcommons-lang-java, 
> libcommons-logging-java, libecj-java, libgeronimo-jpa-2.0-spec-java, 
> libhibernate3-java, libhttpclient-java, libicu4j-java, libitext-java (>= 
> 2.1.7-11~), libjackson2-annotations-java, libjackson2-core-java, 
> libjackson2-databind-java, libjaxen-java, libjaxp1.3-java, libjcommon-java, 
> libjexcelapi-java, libjfreechart-java, liblucene4.10-java (>= 
> 4.10.4+dfsg-2~), libmaven-javadoc-plugin-java, libmondrian-java (>= 
> 1:3.11.0.1-4~), libolap4j-java, librhino-java, libspring-beans-java, 
> libspring-core-java, libxalan2-java, libxmpcore-java, maven-debian-helper, 
> velocity
> dpkg-deb: building package 'sbuild-build-depends-jasperreports-dummy' in 
> '/<>/resolver-7zFc3z/apt_archive/sbuild-build-depends-jasperreports-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-jasperreports-dummy
> dpkg-scanpackages: info: Wrote 1 entries to output Packages file.
> Ign:1 copy:/<>/resolver-7zFc3z/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-7zFc3z/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-7zFc3z/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-7zFc3z/apt_archive ./ Sources [683 B]
> Get:5 copy:/<>/resolver-7zFc3z/apt_archive ./ Packages [778 B]
> Fetched 2424 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install jasperreports build dependencies (apt-based resolver)
> -
> 
> Installing build dependencies
> 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:
>  sbuild-build-depends-jasperreports-dummy : Depends: libitext-java (>= 
> 2.1.7-11~) but it is not 

Bug#839682: ledger-el: Fails to install if emacs23 is still installed

[Tollef Fog Heen]

Package: ledger-el
Version: 3.1.2~pre1+g3a00e1c+dfsg1-1
Severity: serious

It seems like ledger-el tries to install for all installed emacs
versions, but fails when it hits emacs23:

Setting up ledger-el (3.1.2~pre1+g3a00e1c+dfsg1-1) ...
Install emacsen-common for emacs23
emacsen-common: Handling install of emacsen flavor emacs23
Wrote /etc/emacs23/site-start.d/00debian-vars.elc
Wrote /usr/share/emacs23/site-lisp/debian-startup.elc
Install emacsen-common for emacs24
emacsen-common: Handling install of emacsen flavor emacs24
Wrote /etc/emacs24/site-start.d/00debian-vars.elc
Wrote /usr/share/emacs24/site-lisp/debian-startup.elc
Install ledger-el for emacs23
install/ledger-el: Handling install for emacsen flavor emacs23
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-check.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-commodities.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-complete.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-exec.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-fontify.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-fonts.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-init.elc

In toplevel form:
ledger-mode.el:51:1:Error: Required feature `cl-macs' was not provided
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-navigate.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-occur.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-post.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-reconcile.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-regex.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-report.elc

In toplevel form:
ledger-schedule.el:35:1:Error: Required feature `cl-macs' was not provided
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-sort.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-state.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-test.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-texi.elc
Wrote /usr/share/emacs23/site-lisp/ledger-el/ledger-xact.elc
ERROR: install script from ledger-el package failed
dpkg: error processing package ledger-el (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 ledger-el
E: Sub-process /usr/bin/dpkg returned an error code (1)

It should probably not try to install itself for emacs23.

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

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

Versions of packages ledger-el depends on:
ii  emacsen-common  2.0.8

ledger-el recommends no packages.

Versions of packages ledger-el suggests:
ii  ledger  3.1.2~pre1+g3a00e1c+dfsg1-1

-- no debconf information

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

Processed: fixed in stretch mysql-server-5.6_5.6.30-1

[Debian Bug Tracking System]

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

> fixed 798080 5.6.30-1
Bug #798080 [mysql-server-5.6] mysql-server-5.6: service stop hangs forever on 
systemd
Marked as fixed in versions mysql-5.6/5.6.30-1.
> fixed 798080 5.7.13-1~exp1
Bug #798080 [mysql-server-5.6] mysql-server-5.6: service stop hangs forever on 
systemd
There is no source info for the package 'mysql-server-5.6' at version 
'5.7.13-1~exp1' with architecture ''
Unable to make a source version for version '5.7.13-1~exp1'
Ignoring request to alter fixed versions of bug #798080 to the same values 
previously set
> tags 798080 + fixed fixed-upstream fixed-in-experimental
Bug #798080 [mysql-server-5.6] mysql-server-5.6: service stop hangs forever on 
systemd
Added tag(s) fixed, fixed-upstream, and fixed-in-experimental.
>
End of message, stopping processing here.

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

Bug#839309: marked as done (orthanc-postgresql: FTBFS: -- Could NOT find PostgreSQL (missing: PostgreSQL_TYPE_INCLUDE_DIR) (found version "9.6.0"))

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 17:47:34 +
with message-id 
and subject line Bug#839309: fixed in orthanc-postgresql 2.0-3
has caused the Debian Bug report #839309,
regarding orthanc-postgresql: FTBFS: -- Could NOT find PostgreSQL (missing:  
PostgreSQL_TYPE_INCLUDE_DIR) (found version "9.6.0")
to be marked as done.

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

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


-- 
839309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc-postgresql
Version: 2.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -DCMAKE_SKIP_RPATH:BOOL=ON -DSTATIC_BUILD:BOOL=OFF 
> -DUSE_GTEST_DEBIAN_SOURCE_PACKAGE:BOOL=ON -DCMAKE_BUILD_TYPE=""   
>   cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON 
> -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_SKIP_RPATH:BOOL=ON 
> -DSTATIC_BUILD:BOOL=OFF -DUSE_GTEST_DEBIAN_SOURCE_PACKAGE:BOOL=ON 
> -DCMAKE_BUILD_TYPE=
> -- The C compiler identification is GNU 6.2.0
> -- The CXX compiler identification is GNU 6.2.0
> -- Check for working C compiler: /usr/bin/cc
> -- Check for working C compiler: /usr/bin/cc -- works
> -- Detecting C compiler ABI info
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> -- Check for working CXX compiler: /usr/bin/c++
> -- Check for working CXX compiler: /usr/bin/c++ -- works
> -- Detecting CXX compiler ABI info
> -- Detecting CXX compiler ABI info - done
> -- Detecting CXX compile features
> -- Detecting CXX compile features - done
> -- Found PythonInterp: /usr/bin/python (found version "2.7.12") 
> -- Looking for include file uuid/uuid.h
> -- Looking for include file uuid/uuid.h - found
> -- Boost version: 1.61.0
> -- Looking for pthread.h
> -- Looking for pthread.h - found
> -- Looking for pthread_create
> -- Looking for pthread_create - not found
> -- Looking for pthread_create in pthreads
> -- Looking for pthread_create in pthreads - not found
> -- Looking for pthread_create in pthread
> -- Looking for pthread_create in pthread - found
> -- Found Threads: TRUE  
> -- Boost version: 1.61.0
> -- Found the following Boost libraries:
> --   filesystem
> --   thread
> --   system
> --   date_time
> --   regex
> --   locale
> --   chrono
> --   atomic
> JsonCpp include dir: /usr/include/jsoncpp
> -- Looking for C++ include /usr/include/jsoncpp/json/reader.h
> -- Looking for C++ include /usr/include/jsoncpp/json/reader.h - found
> -- Could NOT find PostgreSQL (missing:  PostgreSQL_TYPE_INCLUDE_DIR) (found 
> version "9.6.0")
> -- Looking for C++ include orthanc/OrthancCppDatabasePlugin.h
> -- Looking for C++ include orthanc/OrthancCppDatabasePlugin.h - found
> Setting the version of the libraries to 2.0
> CMake Error: The following variables are used in this project, but they are 
> set to NOTFOUND.
> Please set them or make sure they are set and tested correctly in the CMake 
> files:
> PostgreSQL_TYPE_INCLUDE_DIR (ADVANCED)
>used as include directory in directory /<>
>used as include directory in directory /<>
>used as include directory in directory /<>
>used as include directory in directory /<>
>used as include directory in directory /<>
>used as include directory in directory /<>
>used as include directory in directory /<>
>used as include directory in directory /<>
>used as include directory in directory /<>
> 
> -- Configuring incomplete, errors occurred!
> See also "/<>/Build/CMakeFiles/CMakeOutput.log".
> See also "/<>/Build/CMakeFiles/CMakeError.log".
>   "tail -v -n +0 CMakeCache.txt"
> ==> CMakeCache.txt <==
> # This is the CMakeCache file.
> # For build in directory: /<>/Build
> # It was generated by CMake: /usr/bin/cmake
> # You can edit this file to change values found and used by cmake.
> # If you do not want to change any of the values, simply exit the editor.
> # If you do want to change a value, simply edit, save, and exit the editor.
> # The syntax for the file is as follows:
> # KEY:TYPE=VALUE
> # KEY is the name of a variable in the cache.
> # TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
> # VALUE is the current value for the KEY.
> 
> 
> # EXTERNAL cache entries

Processed: [bts-link] source package ghostscript

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package ghostscript
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #823100 (http://bugs.debian.org/823100)
> # Bug title: ghostscript: includes two files claimed to be under a non-free 
> Unicode license
> #  * http://bugs.ghostscript.com/show_bug.cgi?id=697121
> #  * remote status changed: UNCONFIRMED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 823100 + fixed-upstream
Bug #823100 [ghostscript] ghostscript: includes two files claimed to be under a 
non-free Unicode license
Added tag(s) fixed-upstream.
> usertags 823100 - status-UNCONFIRMED
Usertags were: status-UNCONFIRMED.
Usertags are now: .
> usertags 823100 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package libmath-gsl-perl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package libmath-gsl-perl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #826192 (http://bugs.debian.org/826192)
> # Bug title: libmath-gsl-perl: FTBFS with GSL 2
> #  * http://rt.cpan.org/Public/Bug/Display.html?id=108378
> #  * remote status changed: open -> resolved
> #  * closed upstream
> tags 826192 + fixed-upstream
Bug #826192 [libmath-gsl-perl] libmath-gsl-perl: FTBFS with GSL 2
Added tag(s) fixed-upstream.
> usertags 826192 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 826192 + status-resolved
There were no usertags set.
Usertags are now: status-resolved.
> thanks
Stopping processing here.

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

Bug#839309: [Debian-med-packaging] Bug#839309: orthanc-postgresql 2.0-3

[Sascha Steinbiss]

Hi Sebastien,

looks good to me, I'm on it.

Cheers
Sascha

> On 3 Oct 2016, at 10:54, Sébastien Jodogne  wrote:
> 
> Hello,
> 
> I have just updated the orthanc-postgresql package:
> https://anonscm.debian.org/viewvc/debian-med?view=revision=22821
> 
> This new version of the package solves the severe FTBFS Bug#839309 
> (orthanc-postgresql: Could NOT find PostgreSQL).
> 
> In the absence of Andreas, please someone could sponsor the upload? TIA!
> 
> Best regards,
> Sébastien-
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging

Bug#839428: marked as done (mono-reference-assemblies: FTBFS: make[7]: gmcs: Command not found)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 16:40:50 +
with message-id 
and subject line Bug#839428: fixed in mono-reference-assemblies 3.12.1+dfsg-2
has caused the Debian Bug report #839428,
regarding mono-reference-assemblies: FTBFS: make[7]: gmcs: Command not found
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.)


-- 
839428: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mono-reference-assemblies
Version: 3.12.1+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory 
> '/<>/mono-reference-assemblies-3.12.1+dfsg/runtime'
> d=`cd ../support && pwd`; \
> sed 
> 's,target="/usr/lib/libMonoPosixHelper.so",target="'$d'/libMonoPosixHelper.la",'
>  ../data/config > etc/mono/configt
> if test -z ""; then :; else \
>   sed 's,target="libgdiplus.so",target="",' etc/mono/configt > 
> etc/mono/configtt; \
>   mv -f etc/mono/configtt etc/mono/configt; fi
> mv -f etc/mono/configt etc/mono/config
> /bin/bash ../mkinstalldirs _tmpinst/bin
> mkdir -p -- _tmpinst/bin
> cp mono-wrapper _tmpinst/bin/mono
> echo '#! /bin/sh' > _tmpinst/bin/ilasm ; \
> r=`pwd`; m=`cd /<>/mono-reference-assemblies-3.12.1+dfsg/mcs && 
> pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/ilasm/ilasm.exe"'" "$@"' >> 
> _tmpinst/bin/ilasm ; \
> chmod +x _tmpinst/bin/ilasm
> echo '#! /bin/sh' > _tmpinst/bin/mcs ; \
> r=`pwd`; m=`cd /<>/mono-reference-assemblies-3.12.1+dfsg/mcs && 
> pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/build/mcs.exe"'" "$@"' 
> >> _tmpinst/bin/mcs ; \
> chmod +x _tmpinst/bin/mcs
> echo '#! /bin/sh' > _tmpinst/bin/gmcs ; \
> r=`pwd`; m=`cd /<>/mono-reference-assemblies-3.12.1+dfsg/mcs && 
> pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/build/mcs.exe -sdk:2"'" 
> "$@"' >> _tmpinst/bin/gmcs ; \
> chmod +x _tmpinst/bin/gmcs
> echo '#! /bin/sh' > _tmpinst/bin/dmcs ; \
> r=`pwd`; m=`cd /<>/mono-reference-assemblies-3.12.1+dfsg/mcs && 
> pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/build/mcs.exe -sdk:4"'" 
> "$@"' >> _tmpinst/bin/dmcs ; \
> chmod +x _tmpinst/bin/dmcs
> echo '#! /bin/sh' > _tmpinst/bin/al2 ; \
> r=`pwd`; m=`cd /<>/mono-reference-assemblies-3.12.1+dfsg/mcs && 
> pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/net_2_0/al.exe"'" "$@"' 
> >> _tmpinst/bin/al2 ; \
> chmod +x _tmpinst/bin/al2
> echo '#! /bin/sh' > _tmpinst/bin/al ; \
> r=`pwd`; m=`cd /<>/mono-reference-assemblies-3.12.1+dfsg/mcs && 
> pwd`; \
> echo 'exec "'"$r/_tmpinst/bin/mono"'" "'"$m/class/lib/net_4_5/al.exe"'" "$@"' 
> >> _tmpinst/bin/al ; \
> chmod +x _tmpinst/bin/al
> if test -w /<>/mono-reference-assemblies-3.12.1+dfsg/mcs; then :; 
> else chmod -R +w /<>/mono-reference-assemblies-3.12.1+dfsg/mcs; fi
> cd /<>/mono-reference-assemblies-3.12.1+dfsg/mcs && make 
> --no-print-directory -s NO_DIR_CHECK=1 PROFILES='net_2_0 net_3_5 net_4_0 
> net_4_5 xbuild_12   ' CC='gcc' all-profiles
> mkdir -p -- build/deps
> make[7]: gmcs: Command not found
> build/profiles/basic.make:92: recipe for target 
> 'build/deps/basic-profile-check.exe' failed
> make[7]: *** [build/deps/basic-profile-check.exe] Error 127

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   
http://aws-logs.debian.net/2016/10/01/mono-reference-assemblies_3.12.1+dfsg-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: mono-reference-assemblies
Source-Version: 3.12.1+dfsg-2

We believe that the bug you reported is fixed in the latest 

Bug#790664: marked as done (FTBFS with new LaTeX: Undefined control sequence / no output PDF file produced)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 16:41:16 +
with message-id 
and subject line Bug#790664: fixed in polyorb 2.11~20140418-3.2
has caused the Debian Bug report #790664,
regarding FTBFS with new LaTeX: Undefined control sequence / no output PDF file 
produced
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.)


-- 
790664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: polyorb
Version: 2.11~20140418-3
Severity: serious

polyorb fails to build in unstable, probably due to the new texlive.

> sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com
...
> This is `epsf.tex' v2.7.4 <14 February 2011>
> ) localization, formatting, and turning on texinfo input format.) (./svn.texi)
> (./polyorb_version.texi) 
> [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]
>  [2] [-1] [-2] (About This Guide)
> Cross reference values unknown; you must run TeX again. [1] Chapter 1 [2]
> [3] [4] [5] Chapter 2 [6] [7] [8] [9] Chapter 3 [10] [11] Chapter 4 [12]
> [13] [14] [15] [16] [17] Chapter 5 [18]
> (./polyorb-setup-tasking-ravenscar.ads.texi [19] [20]) [21] [22] Chapter 6
> [23] [24] [25] [26] [27] [28] [29] (./echo.idl.texi) (./echo-impl.ads.texi
> [30]) (./echo-impl.adb.texi [31]
> ! Undefined control sequence.
> l.60 ("Echoing string: ?
>  " & S (S'First .. L) & " ?");
> ? 
> ! Emergency stop.
> l.60 ("Echoing string: ?
>  " & S (S'First .. L) & " ?");
> !  ==> Fatal error occurred, no output PDF file produced!
> Transcript written on polyorb_ug.log.
> make[2]: *** [polyorb_ug.pdf] Error 1
> Makefile:197: recipe for target 'polyorb_ug.pdf' failed

-- 
Martin Michlmayr
Linux for HP Helion OpenStack, Hewlett-Packard
--- End Message ---
--- Begin Message ---
Source: polyorb
Source-Version: 2.11~20140418-3.2

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated polyorb 
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: Mon, 03 Oct 2016 15:56:15 +0200
Source: polyorb
Binary: polyorb-servers libpolyorb3-dev libpolyorb4 polyorb-doc libpolyorb-dbg
Architecture: source
Version: 2.11~20140418-3.2
Distribution: unstable
Urgency: medium
Maintainer: Xavier Grave 
Changed-By: Gianfranco Costamagna 
Description:
 libpolyorb-dbg - Multiple-personality middleware for Ada (debug)
 libpolyorb3-dev - Multiple-personality middleware for Ada (development)
 libpolyorb4 - Multiple-personality middleware for Ada
 polyorb-doc - Multiple-personality middleware for Ada (documentation)
 polyorb-servers - Multiple-personality middleware for Ada (servers)
Closes: 790664 835966
Changes:
 polyorb (2.11~20140418-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Svante Signell ]
   * debian/patches/examples_corba_echo_echo-impl.adb.patch:
 - fix build failures with some Tex versions
   (Closes: #835966, Closes: #790664).
Checksums-Sha1:
 c1b6bf2fcfd326539b4f31ce92ece491e57e9c95 2406 polyorb_2.11~20140418-3.2.dsc
 1d55502fea7a145ee6dcc303e67fe97851d2a810 34888 
polyorb_2.11~20140418-3.2.debian.tar.xz
Checksums-Sha256:
 58bc3f380572bc7e079e16d061df1d2287bb770fa710c6dcd94defd2baa6cde0 2406 
polyorb_2.11~20140418-3.2.dsc
 174ae80b20538f40c4ac3f085763f503c55b6e54fed8024260b72796728f5ab8 34888 
polyorb_2.11~20140418-3.2.debian.tar.xz
Files:
 19420d97adf2473c1c73128f0eefa90e 2406 net optional 
polyorb_2.11~20140418-3.2.dsc
 710b1d7d9f6cc8172040d06bcff85e65 34888 net optional 
polyorb_2.11~20140418-3.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJX8mUQAAoJEPNPCXROn13Z0YUP/jHfB6N1oHHMQ7EYaMMrYWvt
0s+lgdRjIod2dY0U0GWUjsVbf0PZJQSPz2rszbwxsy6Hif/ziJJtEzRV3owKHy4a
rP9cl0/XUKGxeNrNv4lEETfmCDy4etuKtn+NprwH63Qze+JrMRPIDexYX0w2UD44

Bug#835966: marked as done (RM: polyorb -- RoQA; unmaintained, RC-buggy)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 16:41:16 +
with message-id 
and subject line Bug#835966: fixed in polyorb 2.11~20140418-3.2
has caused the Debian Bug report #835966,
regarding RM: polyorb -- RoQA; unmaintained, RC-buggy
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.)


-- 
835966: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: polyorb
version: 2.11~20140418-3
severity: serious

Dear maintainer,

polyorb is the last package using gnat-4.9 for building, which means
it's the last package holding gnat-4.9 clean removal.

I don't see any activity going on this package, and it already has 2
unaswered RC bugs (#790664 from half 2015).

I wonder if these are signs that calls the removal of the packge.

If I don't receive any reply from you in 2 weeks I'll reassign this bug
to ftpmaster to proceed with the removal.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: polyorb
Source-Version: 2.11~20140418-3.2

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated polyorb 
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: Mon, 03 Oct 2016 15:56:15 +0200
Source: polyorb
Binary: polyorb-servers libpolyorb3-dev libpolyorb4 polyorb-doc libpolyorb-dbg
Architecture: source
Version: 2.11~20140418-3.2
Distribution: unstable
Urgency: medium
Maintainer: Xavier Grave 
Changed-By: Gianfranco Costamagna 
Description:
 libpolyorb-dbg - Multiple-personality middleware for Ada (debug)
 libpolyorb3-dev - Multiple-personality middleware for Ada (development)
 libpolyorb4 - Multiple-personality middleware for Ada
 polyorb-doc - Multiple-personality middleware for Ada (documentation)
 polyorb-servers - Multiple-personality middleware for Ada (servers)
Closes: 790664 835966
Changes:
 polyorb (2.11~20140418-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Svante Signell ]
   * debian/patches/examples_corba_echo_echo-impl.adb.patch:
 - fix build failures with some Tex versions
   (Closes: #835966, Closes: #790664).
Checksums-Sha1:
 c1b6bf2fcfd326539b4f31ce92ece491e57e9c95 2406 polyorb_2.11~20140418-3.2.dsc
 1d55502fea7a145ee6dcc303e67fe97851d2a810 34888 
polyorb_2.11~20140418-3.2.debian.tar.xz
Checksums-Sha256:
 58bc3f380572bc7e079e16d061df1d2287bb770fa710c6dcd94defd2baa6cde0 2406 
polyorb_2.11~20140418-3.2.dsc
 174ae80b20538f40c4ac3f085763f503c55b6e54fed8024260b72796728f5ab8 34888 
polyorb_2.11~20140418-3.2.debian.tar.xz
Files:
 19420d97adf2473c1c73128f0eefa90e 2406 net optional 
polyorb_2.11~20140418-3.2.dsc
 710b1d7d9f6cc8172040d06bcff85e65 34888 net optional 
polyorb_2.11~20140418-3.2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJX8mUQAAoJEPNPCXROn13Z0YUP/jHfB6N1oHHMQ7EYaMMrYWvt
0s+lgdRjIod2dY0U0GWUjsVbf0PZJQSPz2rszbwxsy6Hif/ziJJtEzRV3owKHy4a
rP9cl0/XUKGxeNrNv4lEETfmCDy4etuKtn+NprwH63Qze+JrMRPIDexYX0w2UD44
M5LqRkH+jAbQQCsgsMR9M91PgI+SEdWBVcXmPa9Nic8e8Vz+bHAcKquXZWGWxziW
o9C6PRjptfjxsJrEVOUYAgGJzPyiU+zlTUDCkx5tV3f7FtQSzp+ND8bQpPww9yct
lI78itwXvWGzTrDwsPsrjvNl4xDrLR2w46aG3d6T0ym3Fsb0k/aiIjVF7e3f2ZsZ
Opck3rH7/5mmh9IZNzGiufxn0pKyojIjs3HpCWBEefLVVz01eOgM+g0WHRCJe54o
KryIBSvXaCKDZkqu6VpV7DYzokaSBjahMOehPZs7+obOSHFkPUUC2TACxNGQ251U
kE4SBpG/Pjpl2na2Bm71K46lQmlcplTmI0qUlLdhVl+wiU92GvY4BveRN8InWB6n
4m0marL2OyP0lUBVpZ+SevSyJ5r8K6INYXN2gA9vYMU2Q9dY5SgFJodoDhIo2KVf
yM19GkzAatTCSMJAZBSUoaeqH6ZIqIV7qRYv1bxNZbKhoD1g0Fe9DdHsdk1pXcRt
UM9OB4CMFOiiSYvfy+Rv
=i7vh

Bug#839666: found jessie

[Neil Williams]

found 839666 2.0.7-1
thanks

-- 


Neil Williams
=
http://www.linux.codehelp.co.uk/



pgpKzIzWNzmOS.pgp
Description: OpenPGP digital signature

Processed: found jessie

[Debian Bug Tracking System]

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

> found 839666 2.0.7-1
Bug #839666 [libapache2-mod-uwsgi] Fails to disable uwsgi module upon purge
Marked as found in versions uwsgi/2.0.7-1.
> thanks
Stopping processing here.

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

Bug#839666: Fails to disable uwsgi module upon purge

[Neil Williams]

Package: libapache2-mod-uwsgi
Version: 2.0.12-7
Severity: critical
File: /etc/apache2/mods-available/uwsgi.load
Justification: breaks unrelated software

libapache2-mod-uwsgi provides /etc/apache2/mods-available/proxy_uwsgi.load
and /usr/lib/apache2/modules/mod_proxy_uwsgi.so and enables the module in
the postinst:
apache2_invoke enmod @@module_name@@  || exit 1
https://sources.debian.net/src/uwsgi/2.0.12-7/debian/libapache2-mod-__MODULE__.postinst.in/

However, 
https://sources.debian.net/src/uwsgi/2.0.12-7/debian/libapache2-mod-__MODULE__.prerm.in/
 seems to fail to dismod on purge:

Original log is from jessie:

$ sudo apt --purge remove  libapache2-mod-uwsgi libapache2-mod-wsgi
Removing libapache2-mod-uwsgi (2.0.7-1) ...
Purging configuration files for libapache2-mod-uwsgi (2.0.7-1) ...
Removing libapache2-mod-wsgi (4.3.0-1) ...
ERROR: Can't open /etc/apache2/mods-enabled/uwsgi.load: No such file or 
directoryModule wsgi disabled.
apache2_invoke prerm: Disable module wsgi
apache2_reload: Your configuration is broken. Not restarting Apache 2
apache2_reload: apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: 
Could not open configuration file /etc/apache2/mods-enabled/uwsgi.load: No such 
file or directory
Purging configuration files for libapache2-mod-wsgi (4.3.0-1) ...
apache2_invoke postrm: Purging state for wsgi

Not restarting Apache on a server which is providing multiple hosts is
very bad, especially as apt|dpkg exits cleanly. Unless the admin is
watching the purge output directly, the reason for the server going
offline would not be obvious.

Once the problem is spotted:
$ sudo a2dismod uwsgi
$ sudo apache2ctl restart

... does allow apache to restart successfully.

Reproduced in a sid VM:
$ sudo apt install libapache2-mod-uwsgi libapache2-mod-wsgi

$ sudo apache2ctl -M|grep wsgi
AH00558: apache2: Could not reliably determine the server's fully qualified 
domain name, using 127.0.1.1. Set the 'ServerName' directive globally to 
suppress this message
 uwsgi_module (shared)
 wsgi_module (shared)
neil@debian-sid:~$ sudo apt --purge remove libapache2-mod-uwsgi 
libapache2-mod-wsgi
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libjansson4 libmatheval1 libpython2.7 libsodium18 libyaml-0-2 libzmq5
  uwsgi-core
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  libapache2-mod-uwsgi* libapache2-mod-wsgi*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 342 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 46879 files and directories currently installed.)
Removing libapache2-mod-uwsgi (2.0.12-7) ...
Removing libapache2-mod-wsgi (4.5.7-1) ...
Module wsgi disabled.
apache2_invoke prerm: Disable module wsgi
apache2_reload: Your configuration is broken. Not restarting Apache 2
apache2_reload: apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: 
Syntax error on line 1 of /etc/apache2/mods-enabled/uwsgi.load: Cannot load 
/usr/lib/apache2/modules/mod_uwsgi.so into server: 
/usr/lib/apache2/modules/mod_uwsgi.so: cannot open shared object file: No such 
file or directory
(Reading database ... 46865 files and directories currently installed.)
Removing libapache2-mod-wsgi (4.5.7-1) ...
Purging configuration files for libapache2-mod-wsgi (4.5.7-1) ...
apache2_invoke postrm: Purging state for wsgi
Removing libapache2-mod-uwsgi (2.0.12-7) ...
Purging configuration files for libapache2-mod-uwsgi (2.0.12-7) ...


$ sudo service apache2 restart
Job for apache2.service failed because the control process exited with error 
code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
$ sudo service apache2 status
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: 
enabled)
   Active: failed (Result: exit-code) since Mon 2016-10-03 17:22:08 BST; 3s ago
  Process: 27997 ExecStop=/usr/sbin/apachectl stop (code=exited, 
status=1/FAILURE)
  Process: 28004 ExecStart=/usr/sbin/apachectl start (code=exited, 
status=1/FAILURE)
 Main PID: 27843 (code=exited, status=0/SUCCESS)

Oct 03 17:22:08 debian-sid systemd[1]: apache2.service: Failed with result 
'exit-code'.
Oct 03 17:22:08 debian-sid systemd[1]: Starting The Apache HTTP Server...
Oct 03 17:22:08 debian-sid apachectl[28004]: apache2: Syntax error on line 140 
of /etc/apache2/apache2.conf: Could not open configuration file
Oct 03 17:22:08 debian-sid apachectl[28004]: Action 'start' failed.
Oct 03 17:22:08 debian-sid apachectl[28004]: The Apache error log may have more 
information.
Oct 03 17:22:08 debian-sid systemd[1]: apache2.service: Control process exited, 
code=exited status=1
Oct 03 17:22:08 debian-sid systemd[1]: Failed to start The Apache HTTP Server.
Oct 03 17:22:08 debian-sid systemd[1]: apache2.service: Unit entered failed 

Bug#839659: libgd2: CVE-2016-7568: Integer overflow in gdImageWebpCtx

[Salvatore Bonaccorso]

Source: libgd2
Version: 2.2.3-3
Severity: grave
Tags: security patch upstream fixed-upstream
Justification: user security hole
Forwarded: https://github.com/libgd/libgd/issues/308

Hi,

the following vulnerability was published for libgd2.

CVE-2016-7568[0]:
| Integer overflow in the gdImageWebpCtx function in gd_webp.c in the GD
| Graphics Library (aka libgd) through 2.2.3, as used in PHP through
| 7.0.11, allows remote attackers to cause a denial of service
| (heap-based buffer overflow) or possibly have unspecified other impact
| via crafted imagewebp and imagedestroy calls.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-7568
[1] https://github.com/libgd/libgd/issues/308
[2] 
https://github.com/libgd/libgd/commit/40bec0f38f50e8510f5bb71a82f516d46facde03

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #790664 [polyorb] FTBFS with new LaTeX: Undefined control sequence / no 
output PDF file produced
Added tag(s) patch and pending.

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

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

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #835966 [src:polyorb] RM: polyorb -- RoQA; unmaintained, RC-buggy
Added tag(s) patch and pending.

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

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

[Gianfranco Costamagna]

control: tags -1 patch pending

> because I could not figure what your patches actually did, and building
> without it just worked.
> I didn't manually close the bug (that I would have otherwise do) because
> I believe that's the maintainer responsability.
> 
> I also didn't close #835966 because, well, the package is in mess right
> now.

since there is some reasons to close this one, since we have maintainer and a 
sponsor.
I'm nmuing it again, with the additional pdf patch  in a few minutes.
(and moreover we got rid of old gnat dependency)

G.
diff -Nru polyorb-2.11~20140418/debian/changelog 
polyorb-2.11~20140418/debian/changelog
--- polyorb-2.11~20140418/debian/changelog  2016-09-19 16:20:50.0 
+0200
+++ polyorb-2.11~20140418/debian/changelog  2016-10-03 16:02:52.0 
+0200
@@ -1,3 +1,14 @@
+polyorb (2.11~20140418-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Svante Signell ]
+  * debian/patches/examples_corba_echo_echo-impl.adb.patch:
+- fix build failures with some Tex versions
+  (Closes: #835966, Closes: #790664).
+
+ -- Gianfranco Costamagna   Mon, 03 Oct 2016 
15:56:15 +0200
+
 polyorb (2.11~20140418-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru 
polyorb-2.11~20140418/debian/patches/examples_corba_echo_echo-impl.adb.patch 
polyorb-2.11~20140418/debian/patches/examples_corba_echo_echo-impl.adb.patch
--- 
polyorb-2.11~20140418/debian/patches/examples_corba_echo_echo-impl.adb.patch
1970-01-01 01:00:00.0 +0100
+++ 
polyorb-2.11~20140418/debian/patches/examples_corba_echo_echo-impl.adb.patch
2016-10-03 15:58:05.0 +0200
@@ -0,0 +1,11 @@
+--- a/examples/corba/echo/echo-impl.adb.orig   2014-03-20 21:52:43.0 
+0100
 b/examples/corba/echo/echo-impl.adb2016-09-02 
12:11:41.916884091 +0200
+@@ -55,7 +55,7 @@
+  S (L - 2 .. L) := (others => '.');
+   end if;
+   Ada.Text_IO.Put_Line
+-("Echoing string: « " & S (S'First .. L) & " »");
++("Echoing string: << " & S (S'First .. L) & " >>");
+   return Mesg;
+end EchoString;
+ 
diff -Nru polyorb-2.11~20140418/debian/patches/series 
polyorb-2.11~20140418/debian/patches/series
--- polyorb-2.11~20140418/debian/patches/series 2016-09-19 14:49:16.0 
+0200
+++ polyorb-2.11~20140418/debian/patches/series 2016-10-03 15:56:15.0 
+0200
@@ -44,3 +44,4 @@
 support-tilde-in-pathname.patch
 make-clean.patch
 add-missing-include.patch
+examples_corba_echo_echo-impl.adb.patch


signature.asc
Description: OpenPGP digital signature

Bug#838630: doona: failed with the error message Can't locate object method "new" via package "bedmod::http"

[Hugo Lefeuvre]

Hi Raphaël, Gianfranco,

> well, we can do a repack upload if you want...
> sorry for the issues I caused, I used the gbp command to recreate the tarball,
> and I'm not even sure about where/how to find the orig tarball that kali uses
> (I checkouted the git repo)

You can download it using dget:
dget http://http.kali.org/pool/main/d/doona/doona_1.0+git20160212-0kali1.dsc

the shasums differ, but the contents of the tarballs are identical, according
to diff -r.

Cheers,
 Hugo

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


signature.asc
Description: PGP signature

Bug#838630: doona: failed with the error message Can't locate object method "new" via package "bedmod::http"

[Raphael Hertzog]

Hi,

On Mon, 03 Oct 2016, Gianfranco Costamagna wrote:
> well, we can do a repack upload if you want...

Nope, it's OK, I already dealt with it on my side.

> sorry for the issues I caused, I used the gbp command to recreate the tarball,
> and I'm not even sure about where/how to find the orig tarball that kali uses
> (I checkouted the git repo)

We use "pristine-tar" on all our packaging repositories (otherwise you can
just grab it from any mirror in the pool directly: http://http.kali.org/pool/)

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#839348: marked as done (python-sklearn: wrong import of "parallel")

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 13:20:56 +
with message-id 
and subject line Bug#839348: fixed in scikit-learn 0.18-2
has caused the Debian Bug report #839348,
regarding python-sklearn: wrong import of "parallel"
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.)


-- 
839348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astroml
Version: 0.3-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160930 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> pyversions: missing X(S)-Python-Version in control file, fall back to 
> debian/pyversions
> pyversions: missing debian/pyversions file, fall back to supported versions
> py3versions: no X-Python3-Version in control file, using supported versions
> dh build --with python2,python3 --buildsystem=pybuild
>dh_testdir -O--buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/decorators.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/py3k_compat.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/lumfunc.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/filters.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/correlation.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/crossmatch.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/utils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/resample.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/fourier.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/cosmology.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> copying astroML/sum_of_norms.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML
> creating /<>/.pybuild/pythonX.Y_2.7/build/astroML/tests
> copying astroML/tests/test_pickle_results.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/tests
> copying astroML/tests/test_filters.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/tests
> copying astroML/tests/test_utils.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/tests
> copying astroML/tests/test_fourier.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/tests
> copying astroML/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/tests
> copying astroML/tests/test_resample.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/tests
> creating /<>/.pybuild/pythonX.Y_2.7/build/astroML/clustering
> copying astroML/clustering/mst_clustering.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/clustering
> copying astroML/clustering/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/clustering
> creating 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/clustering/tests
> copying astroML/clustering/tests/test_MST_clustering.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/clustering/tests
> copying astroML/clustering/tests/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/clustering/tests
> creating /<>/.pybuild/pythonX.Y_2.7/build/astroML/classification
> copying astroML/classification/gmm_bayes.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/classification
> copying astroML/classification/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/classification
> creating /<>/.pybuild/pythonX.Y_2.7/build/astroML/linear_model
> copying astroML/linear_model/linear_regression.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/linear_model
> copying astroML/linear_model/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/linear_model
> copying astroML/linear_model/kernel_regression.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/linear_model
> copying astroML/linear_model/TLS.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/linear_model
> creating /<>/.pybuild/pythonX.Y_2.7/build/astroML/datasets
> copying astroML/datasets/sdss_specgals.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/astroML/datasets
> copying 

Bug#838630: doona: failed with the error message Can't locate object method "new" via package "bedmod::http"

[Gianfranco Costamagna]

Hi,


>Thanks for handling this. But I just see that you uploaded a .orig.tar.gz
>that does not match the one we used in Kali and is creating me tedious
>work to clean up the situation.


well, we can do a repack upload if you want...
sorry for the issues I caused, I used the gbp command to recreate the tarball,
and I'm not even sure about where/how to find the orig tarball that kali uses
(I checkouted the git repo)

sorry again, I'll try to be more careful next time indeed :)

G.

Bug#839010: CVE-2016-2776 and sid?

[Aleksi Suhonen]

Hello,

Does the patch for this bug clash with some Debian special patch, or why
isn't it being applied to the sid package?

Best regards,

-- 
Aleksi Suhonen

() ascii ribbon campaign
/\ support plain text e-mail

Bug#837026: marked as done (tcsh: FTBFS: sh.proc.c:155:16: error: storage size of 'w' isn't known)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 13:04:17 +
with message-id 
and subject line Bug#837026: fixed in tcsh 6.18.01-5.1
has caused the Debian Bug report #837026,
regarding tcsh: FTBFS: sh.proc.c:155:16: error: storage size of 'w' isn't known
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.)


-- 
837026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcsh
Version: 6.18.01-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160906 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> gcc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -D_FILE_OFFSET_BITS=64 -I. -I. 
> -D_PATH_TCSHELL='"/usr/bin/tcsh"'  -Wdate-time -D_FORTIFY_SOURCE=2  sh.proc.c
> In file included from /usr/include/signal.h:28:0,
>  from sh.h:39,
>  from sh.proc.c:33:
> /usr/include/features.h:148:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>  # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
>^~~
> sh.proc.c: In function 'pchild':
> sh.proc.c:155:16: error: storage size of 'w' isn't known
>  union wait w;
> ^
> Makefile:465: recipe for target 'sh.proc.o' failed
> make[2]: *** [sh.proc.o] Error 1

The full build log is available from:
   http://people.debian.org/~lucas/logs/2016/09/06/tcsh_6.18.01-5_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: tcsh
Source-Version: 6.18.01-5.1

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated tcsh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Sep 2016 11:52:55 +0100
Source: tcsh
Binary: tcsh
Architecture: source amd64
Version: 6.18.01-5.1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Lange 
Changed-By: Alastair McKinstry 
Description:
 tcsh   - TENEX C Shell, an enhanced version of Berkeley csh
Closes: 833965 837026
Changes:
 tcsh (6.18.01-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * FTBFS when trying to use BSD WAIT type. Closes: #837026, #833965
   * Add -D_DEFAULT_SOURCE to CFLAGS
Checksums-Sha1:
 1aa111e2a4d04d1a3410d25b8578b675f76bed45 1781 tcsh_6.18.01-5.1.dsc
 50839c63514e3948917949053063635b7ce070f8 23907 tcsh_6.18.01-5.1.diff.gz
 979957fc0933c7bff1046ec5d2480cecbe48e802 525696 
tcsh-dbgsym_6.18.01-5.1_amd64.deb
 fb5b15c0b860e640623b19b1427dd87e1923b593 456406 tcsh_6.18.01-5.1_amd64.deb
Checksums-Sha256:
 230ff577250d3000432925e7c62668e6e22e6010ed91ce728c0ca690b9d9eb01 1781 
tcsh_6.18.01-5.1.dsc
 fea859fd7d0b06d9ef7879dcb837d60f4bcafc231008a9a1240b8baa35a63d90 23907 
tcsh_6.18.01-5.1.diff.gz
 390f218458228c2ca54e144e5a333651dee5b273f682fbb6b4f0d12171344b04 525696 
tcsh-dbgsym_6.18.01-5.1_amd64.deb
 c2b20149e8135d95d4ffccbca9a09a929bb85d4993e6e83397daf778b463c08c 456406 
tcsh_6.18.01-5.1_amd64.deb
Files:
 3c702d587881f0dfc15e966123460c85 1781 shells optional tcsh_6.18.01-5.1.dsc
 085ba0c412361e21c45de3c19951030b 23907 shells optional tcsh_6.18.01-5.1.diff.gz
 27e276c5fe4d423bcac0f8690865f894 525696 debug extra 
tcsh-dbgsym_6.18.01-5.1_amd64.deb
 eb0d714c1b60d44bb8478fb43a3e3fbe 456406 shells optional 
tcsh_6.18.01-5.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX7kdPAAoJEMvmu05dmtOl2lAP/0ssDVsS4ieRVNLDjWi7X3O9

Bug#833965: marked as done (tcsh: uses deprecated BSD union wait type)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 13:04:17 +
with message-id 
and subject line Bug#833965: fixed in tcsh 6.18.01-5.1
has caused the Debian Bug report #833965,
regarding tcsh: uses deprecated BSD union wait type
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.)


-- 
833965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833965
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcsh
Version: 6.18.01-5
Severity: important
Tags: patch upstream fixed-upstream

Dear Maintainer,

glibc 2.24 has removed the deprecated BSD union wait type if favor of
the POSIX 1 interface using W* macros from  (such as
WEXITSTATUS).

glibc 2.24 is already available in experimental and will plan to upload
it to sid in the next days/weeks. This will cause tcsh to fail to build
from source. You will find attached a patch taken from upstream to fix
the issue. I had to backport the muslc patch to make the glibc 2.24
patch apply without any change.

Please also note that this will not break the existing binaries, just
building the package from source.

Thanks,
Aurelien

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: tcsh
Source-Version: 6.18.01-5.1

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated tcsh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 30 Sep 2016 11:52:55 +0100
Source: tcsh
Binary: tcsh
Architecture: source amd64
Version: 6.18.01-5.1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Lange 
Changed-By: Alastair McKinstry 
Description:
 tcsh   - TENEX C Shell, an enhanced version of Berkeley csh
Closes: 833965 837026
Changes:
 tcsh (6.18.01-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * FTBFS when trying to use BSD WAIT type. Closes: #837026, #833965
   * Add -D_DEFAULT_SOURCE to CFLAGS
Checksums-Sha1:
 1aa111e2a4d04d1a3410d25b8578b675f76bed45 1781 tcsh_6.18.01-5.1.dsc
 50839c63514e3948917949053063635b7ce070f8 23907 tcsh_6.18.01-5.1.diff.gz
 979957fc0933c7bff1046ec5d2480cecbe48e802 525696 
tcsh-dbgsym_6.18.01-5.1_amd64.deb
 fb5b15c0b860e640623b19b1427dd87e1923b593 456406 tcsh_6.18.01-5.1_amd64.deb
Checksums-Sha256:
 230ff577250d3000432925e7c62668e6e22e6010ed91ce728c0ca690b9d9eb01 1781 
tcsh_6.18.01-5.1.dsc
 fea859fd7d0b06d9ef7879dcb837d60f4bcafc231008a9a1240b8baa35a63d90 23907 
tcsh_6.18.01-5.1.diff.gz
 390f218458228c2ca54e144e5a333651dee5b273f682fbb6b4f0d12171344b04 525696 
tcsh-dbgsym_6.18.01-5.1_amd64.deb
 c2b20149e8135d95d4ffccbca9a09a929bb85d4993e6e83397daf778b463c08c 456406 
tcsh_6.18.01-5.1_amd64.deb
Files:
 3c702d587881f0dfc15e966123460c85 1781 shells optional tcsh_6.18.01-5.1.dsc
 085ba0c412361e21c45de3c19951030b 23907 shells optional tcsh_6.18.01-5.1.diff.gz
 27e276c5fe4d423bcac0f8690865f894 525696 debug extra 
tcsh-dbgsym_6.18.01-5.1_amd64.deb
 eb0d714c1b60d44bb8478fb43a3e3fbe 456406 shells optional 
tcsh_6.18.01-5.1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX7kdPAAoJEMvmu05dmtOl2lAP/0ssDVsS4ieRVNLDjWi7X3O9
lkxSXGCue6JoG9F1Pn9P5/PMYFFb8lpoHcGVQXt2xwsYlwusIGyWMULwdXBBLFKJ
E6mspA7yaxUhf6VIINT8fzPY8HJS0pOTW+pQ2HIZayvaA+9m4QnpkbByDouJRIKH
M5n6onESOXISOgQs0dFMoM3JClGgsXb3ju/Jq3gXfNhBdmsae59qjCZunPGg3r/2
4dcSLbA4mgFCW2sTVTzGjj4dF7W8kj71QI1u85x1MAcSChWlRPbtNGkHlWbm61qY
u0gBIXcP8O5WKiXNLTb23biz/RuWxecZnyeqkDhcM++o2r2vw1A9Jr5ZjFD6kwJB
8GZKmRONMYd0XK1shRqHFZHiEdmsHEhIcwdHte5l8agBQVAbaviPtfZN79vcUxTS
+56IHaYy81nSaM17fL2mt/K5SPIKzKt0KbvNOzMVnzbxJKfZWuNERJOBenOgaCcQ

Bug#806867: python-scipy: FTBFS when built with dpkg-buildpackage -A (No module named scipy)

[Julian Taylor]

On 24.09.2016 23:26, Julian Taylor wrote:
> On 24.09.2016 23:14, Sebastian Humenda wrote:
>> Just to let people know: I'm working on it and hope to upload a new package
>> shortly.
>>
> 
> hm I wanted to do it tomorrow, but if you have it done go ahead.
> note there is a new upstream version that should be uploaded to fix
> other issues.
> 

where did you get the tarball from that you pushed to git?
its different from what uscan pulls and is missing all the documentation.



signature.asc
Description: OpenPGP digital signature

Bug#837532: [Debichem-devel] Bug#837532: mpqc3: FTBFS (Libint library is too old: a recent beta of 2.1.0 is required)

[Michael Banck]

OK, so I've uploaded a new mpqc3 package which excludes the problematic
check in external/Libint, but it stills FTBFS - there's been too much
APi breakage between beta2 and final apparently and mpqc3 has not been
ported yet. Which is kinda annoying cause both are maintained by the
same upstream authors.

I'll see whether I can do something myself about this, but I'm no
specialist in this kind of C++.

In any case, it seems those issues about missing math headers no longer
shows up? Oh, I now checked again and mips64el and hppa seems to exhibit
that behaviour still:

https://buildd.debian.org/status/fetch.php?pkg=mpqc3=mips64el=0.0~git20160216-5=1475465771
https://buildd.debian.org/status/fetch.php?pkg=mpqc3=hppa=0.0%7Egit20160216-5=1475461952

So maybe this bug should get unmerged and reopened, and a second one
about the 2.1.0 final libint2 interface opened, bah.


Michael

Processed: found 777525 in 0.10.2-1

[Debian Bug Tracking System]

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

> # add a found version for unstable
> found 777525 0.10.2-1
Bug #777525 [rope] rope: CVE-2014-3539
There is no source info for the package 'rope' at version '0.10.2-1' with 
architecture ''
Unable to make a source version for version '0.10.2-1'
Marked as found in versions 0.10.2-1.
> thanks
Stopping processing here.

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

Bug#839019: marked as done (gsoap: FTBFS with -j16)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 12:36:33 +
with message-id 
and subject line Bug#839019: fixed in gsoap 2.8.35-3
has caused the Debian Bug report #839019,
regarding gsoap: FTBFS with -j16
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.)


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

The package FTBFS with -j16:
| make[5]: Entering directory '/<>/gsoap/src'
| /bin/bash ../../ylwrap soapcpp2_yacc.y y.tab.c soapcpp2_yacc.c y.tab.h `echo 
soapcpp2_yacc.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx / -e 
s/c++$/h++/ -e s/c$/h/` y.output soapcpp2_yacc.output -- bison -y -d -v
| /bin/bash ../../ylwrap soapcpp2_lex.l lex.yy.c soapcpp2_lex.c -- flex -l
| gcc -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2 
-DWITH_BISON -DWITH_FLEX  -DSOAPCPP2_IMPORT_PATH="\"/usr/share/gsoap/impor t\"" 
-DLINUX -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -MT soapcpp2-symbol2.o - MD -MP -MF 
.deps/soapcpp2-symbol2.Tpo -c -o soapcpp2-symbol2.o `test -f 'symbol2.c' || 
echo './'`symbol2.c
| gcc -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2 
-DWITH_BISON -DWITH_FLEX  -DSOAPCPP2_IMPORT_PATH="\"/usr/share/gsoap/impor t\"" 
-DLINUX -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -MT soapcpp2-error2.o -M D -MP -MF 
.deps/soapcpp2-error2.Tpo -c -o soapcpp2-error2.o `test -f 'error2.c' || echo 
'./'`error2.c
| gcc -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2 
-DWITH_BISON -DWITH_FLEX  -DSOAPCPP2_IMPORT_PATH="\"/usr/share/gsoap/impor t\"" 
-DLINUX -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -MT soapcpp2-init2.o -MD  -MP -MF 
.deps/soapcpp2-init2.Tpo -c -o soapcpp2-init2.o `test -f 'init2.c' || echo 
'./'`init2.c
| gcc -DHAVE_CONFIG_H -I. -I../..   -Wdate-time -D_FORTIFY_SOURCE=2 
-DWITH_BISON -DWITH_FLEX  -DSOAPCPP2_IMPORT_PATH="\"/usr/share/gsoap/impor t\"" 
-DLINUX -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -MT soapcpp2-soapcpp2.o  -MD -MP -MF 
.deps/soapcpp2-soapcpp2.Tpo -c -o soapcpp2-soapcpp2.o `test -f 'soapcpp2.c' || 
echo './'`soapcpp2.c
| symbol2.c:40:27: fatal error: soapcpp2_yacc.h: No such file or directory
|  #include "soapcpp2_yacc.h"
|^
| compilation terminated.
| Makefile:507: recipe for target 'soapcpp2-symbol2.o' failed
| make[5]: *** [soapcpp2-symbol2.o] Error 1
| make[5]: *** Waiting for unfinished jobs
| init2.c:39:27: fatal error: soapcpp2_yacc.h: No such file or directory
|  #include "soapcpp2_yacc.h"
|^
| compilation terminated.
| error2.c:39:27: fatal error: soapcpp2_yacc.h: No such file or directory
|  #include "soapcpp2_yacc.h"
|^
| compilation terminated.
| Makefile:535: recipe for target 'soapcpp2-init2.o' failed
| make[5]: *** [soapcpp2-init2.o] Error 1

It succeeded with -j1. Full build log at
  https://breakpoint.cc/gsoap_2.8.35-2_amd64-2016-09-27T19_02_29Z.txt

Sebastian
--- End Message ---
--- Begin Message ---
Source: gsoap
Source-Version: 2.8.35-3

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated gsoap 
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: Mon, 03 Oct 2016 13:20:15 +0200
Source: gsoap
Binary: libgsoap10 libgsoap-dev gsoap gsoap-doc libgsoap-dbg gsoap-dbg
Architecture: source amd64 all
Version: 2.8.35-3
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Description:
 gsoap  - Stub generators for gSOAP
 gsoap-dbg  - Debugging symbols for gSOAP stub generators
 gsoap-doc  - gSOAP documentation
 libgsoap-dbg - 

Processed: bug 839598 is forwarded to https://github.com/golang/go/issues/15628

[Debian Bug Tracking System]

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

> forwarded 839598 https://github.com/golang/go/issues/15628
Bug #839598 [gccgo-6] unable to build gitlab-workhorse with gccgo-6
Set Bug forwarded-to-address to 'https://github.com/golang/go/issues/15628'.
> thanks
Stopping processing here.

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

Bug#838630: doona: failed with the error message Can't locate object method "new" via package "bedmod::http"

[Raphael Hertzog]

On Tue, 27 Sep 2016, Gianfranco Costamagna wrote:
> thanks! I rescheduled to deferred/0, it should go in in a few minutes :)
> I don't change the urgency because I would like to avoid having to git push -f
> and dcut/git clone the repo and so on
> it is a new package, and this is a new release, 5 days should already be 
> enough :)

Thanks for handling this. But I just see that you uploaded a .orig.tar.gz
that does not match the one we used in Kali and is creating me tedious
work to clean up the situation.

I know that you should not have to care about this but since you
mentionned that you grabbed the changes from Kali I thought that
I could tell it to you so that you can pay attention to this next time.

Thank you!

PS: That's how reprepro fails:
File "pool/main/d/doona/doona_1.0+git20160212.orig.tar.gz" is already 
registered with different checksums!
md5 expected: 5364023dd2ec87f9e3b1aeecc2a7c334, got: 
1e10cc3670de27239f198a81704afe72
sha1 expected: 6e174a631d2af9b26e663c62eb30008b8db7f899, got: 
2dd4c31c2aa5d3ecd8d58c460e5fb284194a17c3
sha256 expected: 
1633d60f2aa01b1114791c1551acfa86fce59e56bfe96adb0681fc2e2bcf3428, got: 
9578fe364c1bc60814539fbe51ea3cf312761b1b608770bc5b5adce8829ef82d
size expected: 23939, got: 23603

-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: http://www.freexian.com/services/debian-lts.html
Learn to master Debian: http://debian-handbook.info/get/

Bug#839421: marked as done (smuxi: FTBFS: System.IO.FileNotFoundException: Could not find file "/etc/localtime")

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 12:07:50 +
with message-id 
and subject line Bug#839421: fixed in smuxi 1.0.3-2
has caused the Debian Bug report #839421,
regarding smuxi: FTBFS: System.IO.FileNotFoundException: Could not find file 
"/etc/localtime"
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.)


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

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/lib'
> /usr/bin/xbuild /toolsversion:4.0 /p:TargetFrameworkVersion=v4.5 
> /property:DefineConstants=MONO_4_5 /p:Configuration=Debug 
> /p:SignAssembly=false /p:WarningLevel=0 /p:Warn=0 
> /p:OutputPath=/<>/bin/debug 
> /p:BaseIntermediateOutputPath=/<>/bin/debug/obj/ 
> /p:IntermediateOutputPath=/<>/bin/debug/obj/ 
> /p:DocumentationFile= 
> ./ServiceStack.Text/src/ServiceStack.Text/ServiceStack.Text.csproj
> XBuild Engine Version 12.0
> Mono, Version 4.2.1.0
> Copyright (C) 2005-2013 Various Mono authors
> 
> Unhandled Exception:
> System.IO.FileNotFoundException: Could not find file "/etc/localtime"
> File name: '/etc/localtime'
>   at System.IO.FileStream..ctor (System.String path, FileMode mode, 
> FileAccess access, FileShare share, Int32 bufferSize, Boolean anonymous, 
> FileOptions options) <0x7fcd16d5d2c0 + 0x005ed> in :0 
>   at System.IO.FileStream..ctor (System.String path, FileMode mode, 
> FileAccess access, FileShare share) <0x7fcd16d5cf30 + 0x0004b> in  unknown>:0 
>   at (wrapper remoting-invoke-with-check) System.IO.FileStream:.ctor 
> (string,System.IO.FileMode,System.IO.FileAccess,System.IO.FileShare)
>   at System.IO.File.OpenRead (System.String path) <0x7fcd16d5aa50 + 0x00034> 
> in :0 
>   at System.TimeZoneInfo.FindSystemTimeZoneByFileName (System.String id, 
> System.String filepath) <0x7fcd16cbbfe0 + 0x00032> in :0 
>   at System.TimeZoneInfo.CreateLocal () <0x7fcd16cba850 + 0x00176> in 
> :0 
>   at System.TimeZoneInfo.get_Local () <0x7fcd16cba7c0 + 0x00025> in  unknown>:0 
>   at System.TimeZoneInfo.GetDateTimeNowUtcOffsetFromUtc (DateTime time, 
> System.Boolean& isAmbiguousLocalDst) <0x7fcd16cbbce0 + 0x00017> in  unknown>:0 
>   at System.DateTime.get_Now () <0x7fcd16b64260 + 0x00046> in  unknown>:0 
>   at Microsoft.Build.BuildEngine.Project..ctor 
> (Microsoft.Build.BuildEngine.Engine engine, System.String toolsVersion) 
> <0x417a2d40 + 0x00220> in :0 
>   at Microsoft.Build.BuildEngine.Project..ctor 
> (Microsoft.Build.BuildEngine.Engine engine) <0x417a2cf0 + 0x0001b> in 
> :0 
>   at Microsoft.Build.BuildEngine.Engine.CreateNewProject () <0x417a2ca0 + 
> 0x00037> in :0 
>   at Mono.XBuild.CommandLine.MainClass.Execute () <0x41799680 + 0x00be3> in 
> :0 
>   at Mono.XBuild.CommandLine.MainClass.Main (System.String[] args) 
> <0x41796d70 + 0x0008b> in :0 
> Makefile:1010: recipe for target '../bin/debug/ServiceStack.Text.dll' failed
> make[3]: *** [../bin/debug/ServiceStack.Text.dll] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/smuxi_1.0.3-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: smuxi
Source-Version: 1.0.3-2

We believe that the bug you reported is fixed in the latest version of
smuxi, 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

Bug#820026: icedove crashes suddenly

[bucheron]

Hi there,

Icedove is still crashing each time I abort writing a new email without saving.
The session close, every programs close as well.
It's also happening when saving debian conf files.

+++

Buch'


> Envoyé: mercredi 31 août 2016 à 18:14
> De: "Carsten Schoenert" 
> À: Bucheron 
> Cc: 820...@bugs.debian.org
> Objet: Re: Bug#820026: icedove crashes suddenly
>
> Hello Bucheron,
> 
> Am 31.08.2016 um 17:32 schrieb Bucheron:
> > Hi there,
> > 
> > I'm also triying to understand whats happening with Icedove crashingg.
> > I  can say, it always crashes when i abort writing a new email whithout 
> > saving. It always crash de system, close all the apps and come back to 
> > debian session login.
> > 
> > I hope this message will appear in the thread.
> 
> only if you include the bug address as well to the recipients. :)
> 
> We need a gdb log also to concatenate the the described behaviour with a
> backtrace.
> 
> -- 
> Regards
> Carsten Schoenert
>

Bug#831114: marked as done (travis: FTBFS with GCC 6: stl_algobase.h:265:56: error: macro "max" passed 3 arguments, but takes just 2)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 11:51:26 +
with message-id 
and subject line Bug#831114: fixed in travis 161002-1
has caused the Debian Bug report #831114,
regarding travis: FTBFS with GCC 6: stl_algobase.h:265:56: error: macro "max" 
passed 3 arguments, but takes just 2
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.)


-- 
831114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: travis
Version: 151107-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
> -Wdate-time -D_FORTIFY_SOURCE=2 -c src/raman.cpp -o src/raman.o
> In file included from /usr/include/c++/6/vector:60:0,
>  from src/v_common.h:15,
>  from src/voro++.h:321,
>  from src/vorowrapper.h:29,
>  from src/globalvar.h:31,
>  from src/raman.cpp:28:
> /usr/include/c++/6/bits/stl_algobase.h:265:56: error: macro "max" passed 3 
> arguments, but takes just 2
>  max(const _Tp& __a, const _Tp& __b, _Compare __comp)
> ^
> In file included from src/xvector3.h:29:0,
>  from src/bintools.h:29,
>  from src/moltools.h:29,
>  from src/raman.h:27,
>  from src/raman.cpp:24:
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected unqualified-id 
> before 'const'
>  max(const _Tp& __a, const _Tp& __b)
>  ^
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected ')' before 
> 'const'
> /usr/include/c++/6/bits/stl_algobase.h:219:5: error: expected initializer 
> before 'const'
> In file included from /usr/include/c++/6/vector:60:0,
>  from src/v_common.h:15,
>  from src/voro++.h:321,
>  from src/vorowrapper.h:29,
>  from src/globalvar.h:31,
>  from src/raman.cpp:28:
> /usr/include/c++/6/bits/stl_algobase.h:265:5: error: 'std::max' declared as 
> an 'inline' variable
>  max(const _Tp& __a, const _Tp& __b, _Compare __comp)
>  ^~~
> /usr/include/c++/6/bits/stl_algobase.h:268:7: error: expected 
> primary-expression before 'if'
>if (__comp(__a, __b))
>^~
> /usr/include/c++/6/bits/stl_algobase.h:268:7: error: expected '}' before 'if'
> /usr/include/c++/6/bits/stl_algobase.h:268:7: error: expected ';' before 'if'
> /usr/include/c++/6/bits/stl_algobase.h:270:7: error: expected unqualified-id 
> before 'return'
>return __a;
>^~
> /usr/include/c++/6/bits/stl_algobase.h:315:38: error: 
> 'random_access_iterator_tag' was not declared in this scope
>  struct __copy_move
>   ^~
> /usr/include/c++/6/bits/stl_algobase.h:315:38: note: suggested alternative:
> In file included from /usr/include/c++/6/bits/stl_algobase.h:65:0,
>  from /usr/include/c++/6/vector:60,
>  from src/v_common.h:15,
>  from src/voro++.h:321,
>  from src/vorowrapper.h:29,
>  from src/globalvar.h:31,
>  from src/raman.cpp:28:
> /usr/include/c++/6/bits/stl_iterator_base_types.h:103:10: note:   
> 'std::random_access_iterator_tag'
>struct random_access_iterator_tag : public bidirectional_iterator_tag { };
>   ^~
> In file included from /usr/include/c++/6/vector:60:0,
>  from src/v_common.h:15,
>  from src/voro++.h:321,
>  from src/vorowrapper.h:29,
>  from src/globalvar.h:31,
>  from src/raman.cpp:28:
> /usr/include/c++/6/bits/stl_algobase.h:315:64: error: template argument 3 is 
> invalid
>  struct __copy_move

Bug#811674: fixed in ceph 0.94.5-1.1

[Vincent Lefevre]

On 2016-10-03 10:31:42 +, Mattia Rizzolo wrote:
> it has to be fixed *both* in unstable and experimental if we want to
> eventually be able to remove boost1.58,

OK, I didn't know that experimental was affected too. I thought
that upstream would have added C++11 support in the latest version.
Note that once upstream has done this, the option could be
removed.

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

Bug#812164: marked as done (gnome-chemistry-utils: FTBFS with GCC 6: cannot convert)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 11:34:50 +
with message-id 
and subject line Bug#812164: fixed in gnome-chemistry-utils 0.14.14-1
has caused the Debian Bug report #812164,
regarding gnome-chemistry-utils: FTBFS with GCC 6: cannot convert
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.)


-- 
812164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-chemistry-utils
Version: 0.14.10-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> 
> document.cc: In member function 'void gcr::Document::OnExportVRML(const 
> string&) const':
> document.cc:1524:24: error: cannot convert 'std::ostringstream {aka 
> std::__cxx11::basic_ostringstream}' to 'gpointer {aka void*}' for 
> argument '1' to 'void g_object_unref(gpointer)'
> g_object_unref (file);
> ^
> 
> Makefile:599: recipe for target 'document.lo' failed
> make[4]: *** [document.lo] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: gnome-chemistry-utils
Source-Version: 0.14.14-1

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated gnome-chemistry-utils 
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: Mon, 03 Oct 2016 12:59:12 +0200
Source: gnome-chemistry-utils
Binary: libgcu0v5 gcu-bin gcu-plugin gcrystal gchempaint
Architecture: source amd64
Version: 0.14.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Daniel Leidert 
Description:
 gchempaint - 2D chemical structures editor for the GNOME2 desktop
 gcrystal   - lightweight crystal structures visualizer
 gcu-bin- GNOME chemistry utils (helper applications)
 gcu-plugin - GNOME chemistry utils (browser plugin)
 libgcu0v5  - GNOME chemistry utils (library)
Closes: 812164
Changes:
 gnome-chemistry-utils (0.14.14-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes build issues with GCC 6 (closes: #812164).
   * debian/compat: Raised to level 9.
   * debian/control: Dropped debug package for dbgsym transition.
 (Standards-Version): Raised to 3.9.8.
 (Build-Depends): Raised required versions for libglib2.0-dev and
 libgoffice-0.10-dev. Raised debhelper version for the dbgsym transition.
 Added gnumeric.
   * debian/copyright: Updated.
   * debian/rules (override_dh_strip): Make dbgsym-transition.
   * debian/libgcu0v5.install: Fixed library and plugin paths.
   * debian/gchempaint.install: Ditto.
   * debian/gcu-plugin.install: Ditto.
Checksums-Sha1:
 b58d6ea230fb9c99aad267a51c26c8f5d9416d55 2876 
gnome-chemistry-utils_0.14.14-1.dsc
 463ada6e11b385b583da11262990b45f2cdea926 6661695 
gnome-chemistry-utils_0.14.14.orig.tar.bz2
 a541e247e98ad2c592c7455dcf210361483bfb90 21316 
gnome-chemistry-utils_0.14.14-1.debian.tar.xz
 5c4ba5d40f3d8c19c18e0910df7c1c5fc0a1e073 2296744 
gchempaint-dbgsym_0.14.14-1_amd64.deb
 021dcf335ba200639abcaf48115e2eeb5babbacf 1593622 gchempaint_0.14.14-1_amd64.deb
 1c47bb0561ed5387f8c527659303ba4334c59e0d 140696 
gcrystal-dbgsym_0.14.14-1_amd64.deb
 43a02d4997f507068d4afbf40f8956c70c6a411c 473038 gcrystal_0.14.14-1_amd64.deb
 0d6887fda949d69137e56797f456f2904473386f 649876 

Bug#828044: marked as done (botch FTBFS on mips, mips64el and mipsel, Error: atdgen: Command not found)

[Debian Bug Tracking System]

Your message dated Mon, 3 Oct 2016 10:49:42 +
with message-id <20382c9c3ac3924db9a29d43aa437435528de...@badag02.ba.imgtec.org>
and subject line Bug#828044: fixed in atdgen 1.9.1-2
has caused the Debian Bug report #828044,
regarding botch FTBFS on mips, mips64el and mipsel, Error: atdgen: Command not 
found
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.)


-- 
828044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: botch
Version: 0.17-3
Severity: serious
Tags: sid + patch
Justification: FTBFS
User: debian-m...@lists.debian.org
Usertags: mips-patch

Hello,

Package botch_0.17-3 FTBFS on mips, mipsel and mips64el with following error:

> atdgen -j -j-std datatypes.atd
> make[2]: atdgen: Command not found
> Makefile:130: recipe for target 'datatypes_j.ml' failed
> make[2]: *** [datatypes_j.ml] Error 127

build log:
https://buildd.debian.org/status/fetch.php?pkg=botch=mipsel=0.17-3=1460610554

This problem occurs because there is no atdgen binary file on mips, mips64el 
and mipsel,
instead we could use atdgen.run.

I have created and attached a patch which enable useage of atdgen.run if atdgen 
does not exist.

After applaying this patch, this problem no longer occurs, but there is the 
same problem as well as architectures i386 and amd64:
https://bugs.debian.org/827977


Regards,
Radovan
--- botch-0.17.orig/Makefile	2016-06-22 13:49:38.0 +
+++ botch-0.17/Makefile	2016-06-24 09:26:59.582651725 +
@@ -29,6 +29,7 @@ BIN_TOOLS:=$(BIN_PYTOOLS) $(BIN_OCTOOLS)
 MANPAGES:=$(patsubst %, doc/man/botch-%.1, $(BIN_TOOLS))
 
 OCAML_BEST ?= $(if $(wildcard /usr/bin/ocamlopt),native,byte)
+ATDGEN ?= $(if $(wildcard /usr/bin/atdgen ),atdgen,atdgen.run)
 
 PWD := $(shell pwd)
 BUILD = $(PWD)/dose/_build
@@ -127,10 +128,10 @@ doselib:
 	done
 
 %_j.ml: %.atd
-	atdgen -j -j-std $<
+	$(ATDGEN) -j -j-std $<
 
 %_t.ml: %.atd
-	atdgen -t $<
+	$(ATDGEN) -t $<
 
 .PHONY: atdgen
 atdgen: datatypes_j.ml datatypes_t.ml
--- End Message ---
--- Begin Message ---
Bug is fixed in new version of atdgen package.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837804

Regards,
Radovan--- End Message ---

Bug#811674: marked as done (FTBFS with GCC 6: multiple errors)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 10:34:13 +
with message-id 
and subject line Bug#811674: fixed in ceph 0.80.11-1.1
has caused the Debian Bug report #811674,
regarding FTBFS with GCC 6: multiple errors
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.)


-- 
811674: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph
Version: 0.80.11-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -D__CEPH__ -D_FILE_OFFSET_BITS=64 
> -D_REENTRANT -D_THREAD_SAFE -D__STDC_FORMAT_MACROS -D_GNU_SOURCE 
> -DCEPH_LIBDIR=\"/usr/lib/x86_64-linux-gnu\" 
> -DCEPH_PKGLIBDIR=\"/usr/lib/x86_64-linux-gnu/ceph\" -DGTEST_HAS_TR1_TUPLE=0 
> -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/nss -I/usr/include/nspr -Wall 
> -Wtype-limits -Wignored-qualifiers -Winit-self -Wpointer-arith 
> -Werror=format-security -fno-strict-aliasing -fsigned-char -rdynamic 
> -ftemplate-depth-1024 -Wnon-virtual-dtor -Wno-invalid-offsetof 
> -fno-builtin-malloc -fno-builtin-calloc -fno-builtin-realloc 
> -fno-builtin-free -Wstrict-null-sentinel -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -c osd/OSD.cc  -fPIC -DPIC -o 
> osd/.libs/libosd_la-OSD.o
> In file included from osd/OSD.h:20:0,
>  from osd/ECBackend.h:18,
>  from osd/ECTransaction.cc:21:
> osd/PG.h:790:25: warning: 'template class std::auto_ptr' is deprecated 
> [-Wdeprecated-declarations]
>void build_prior(std::auto_ptr _set);
>  ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from /usr/include/boost/move/algorithm.hpp:32,
>  from /usr/include/boost/move/move.hpp:32,
>  from /usr/include/boost/variant/detail/move.hpp:28,
>  from /usr/include/boost/variant/detail/initializer.hpp:23,
>  from /usr/include/boost/variant/variant.hpp:30,
>  from /usr/include/boost/variant.hpp:17,
>  from osd/ECTransaction.cc:15:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> In file included from osd/OSD.h:20:0,
>  from osd/ECBackend.h:18,
>  from osd/ECTransaction.cc:21:
> osd/PG.h:1633:12: warning: 'template class std::auto_ptr' is 
> deprecated [-Wdeprecated-declarations]
>std::auto_ptr< PriorSet > prior_set;
> ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from /usr/include/boost/move/algorithm.hpp:32,
>  from /usr/include/boost/move/move.hpp:32,
>  from /usr/include/boost/variant/detail/move.hpp:28,
>  from /usr/include/boost/variant/detail/initializer.hpp:23,
>  from /usr/include/boost/variant/variant.hpp:30,
>  from /usr/include/boost/variant.hpp:17,
>  from osd/ECTransaction.cc:15:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> In file included from osd/OSD.h:20:0,
>  from osd/ReplicatedBackend.h:18,
>  from osd/PGBackend.cc:20:
> osd/PG.h:790:25: warning: 'template class std::auto_ptr' is deprecated 
> [-Wdeprecated-declarations]
>void build_prior(std::auto_ptr _set);
>  ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from /usr/include/boost/detail/allocator_utilities.hpp:17,
>  from /usr/include/boost/statechart/detail/memory.hpp:14,
>  from /usr/include/boost/statechart/event.hpp:13,
>  from osd/PG.h:19,
>  from osd/OSD.h:20,
>  from osd/ReplicatedBackend.h:18,
>  from osd/PGBackend.cc:20:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> In 

Bug#811674: fixed in ceph 0.94.5-1.1

[Mattia Rizzolo]

On Mon, Oct 03, 2016 at 10:31:41AM +, Mattia Rizzolo wrote:
> Anyway, I believed I uploaded both versions, experimental and unstable,
> let me check where the latter went...

well, apparently I just forgot to upload, given that locally I also
lacked the ceph_0.80.11-1.1_source.ftp-master.upload file...

uploaded now (directly without delay).  Sorry for the inconvenience.


-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#811674: fixed in ceph 0.94.5-1.1

[Mattia Rizzolo]

control: fixed -1 0.94.5-1.1

On Mon, Oct 03, 2016 at 12:26:54PM +0200, Vincent Lefevre wrote:
> Control: reopen -1
> 
> On 2016-10-01 10:34:58 +, Mattia Rizzolo wrote:
> > Source: ceph
> > Source-Version: 0.94.5-1.1
> 
> I'm reopening the bug since the unstable/testing version is still
> affected. The fix should have been applied to the unstable version
> (0.80.11-1), not to the experimental version. The goal is to solve
> the issue with ceph for the boost1.61 transition:
> 
>   https://release.debian.org/transitions/html/boost1.61.html

it has to be fixed *both* in unstable and experimental if we want to
eventually be able to remove boost1.58, so that was totally fine.  A
closed bug with a fixed version indicating only a version in
experimental is totally fine either, as the bug won't be archived and
will still be marked as affecting unstable.

Anyway, I believed I uploaded both versions, experimental and unstable,
let me check where the latter went...

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Processed: Re: Bug#811674: fixed in ceph 0.94.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.94.5-1.1
Bug #811674 [ceph] FTBFS with GCC 6: multiple errors
Marked as fixed in versions ceph/0.94.5-1.1.

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

Bug#811674: fixed in ceph 0.94.5-1.1

[Vincent Lefevre]

Control: reopen -1

On 2016-10-01 10:34:58 +, Mattia Rizzolo wrote:
> Source: ceph
> Source-Version: 0.94.5-1.1

I'm reopening the bug since the unstable/testing version is still
affected. The fix should have been applied to the unstable version
(0.80.11-1), not to the experimental version. The goal is to solve
the issue with ceph for the boost1.61 transition:

  https://release.debian.org/transitions/html/boost1.61.html

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

Processed: Re: Bug#811674: fixed in ceph 0.94.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #811674 {Done: Mattia Rizzolo } [ceph] FTBFS with GCC 6: 
multiple errors
'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 ceph/0.94.5-1.1.

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

Processed: Re: Bug#712510: fixed in python-whoosh 2.4.1-1

[Debian Bug Tracking System]

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

> severity 712510 minor
Bug #712510 {Done: Dragoslav Sicarov } [python-whoosh] 
python-whoosh FTBFS:some tests failed on mips
Severity set to 'minor' from 'serious'
> thanks
Stopping processing here.

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

Bug#831961: proftpd-dfsg: FTBFS with dpkg-buildpackage -A: make: *** No rule to make target 'build-indep'. Stop.

[Gianfranco Costamagna]

Hi
> We have 3 RC bugs on proftp. For two of them there is a fix in git.
> For the third one I/we do not know how to solve it (tag "help" is set).
> I'd rather upload a fix for all of these three, as the uploaded package
> won't migrate to testing if the third is still present.
> 
> I you disagree drop us a note.
> 

please NMU the package. It is one of the last blockers for hardening-wrapper 
removals, the others are being uploaded right now.

(note: I'm not maintainer, nor uploader for this package)

thanks!

G.



signature.asc
Description: OpenPGP digital signature

Bug#839413: marked as done (ruby-tzinfo should depend on tzdata)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-tzinfo should depend on tzdata
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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-simple-form
Version: 3.2.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-simple-form/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"simple_form\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-simple-form/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/ruby-simple-form/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/action_view_extensions/builder_test.rb" 
> "test/action_view_extensions/form_helper_test.rb" 
> "test/components/label_test.rb" "test/form_builder/association_test.rb" 
> "test/form_builder/button_test.rb" 
> "test/form_builder/error_notification_test.rb" 
> "test/form_builder/error_test.rb" "test/form_builder/general_test.rb" 
> "test/form_builder/hint_test.rb" "test/form_builder/input_field_test.rb" 
> "test/form_builder/label_test.rb" "test/form_builder/wrapper_test.rb" 
> "test/generators/simple_form_generator_test.rb" 
> "test/inputs/boolean_input_test.rb" 
> "test/inputs/collection_check_boxes_input_test.rb" 
> "test/inputs/collection_radio_buttons_input_test.rb" 
> "test/inputs/collection_select_input_test.rb" 
> "test/inputs/datetime_input_test.rb" "test/inputs/disabled_test.rb" 
> "test/inputs/discovery_test.rb" "test/inputs/file_input_test.rb" 
> "test/inputs/general_test.rb" 
> "test/inputs/grouped_collection_select_input_test.rb" 
> "test/inputs/hidden_input_test.rb" "test/inputs/numeric_input_test.rb" 
> "test/inputs/priority_input_test.rb" "test/inputs/readonly_test.rb" 
> "test/inputs/required_test.rb" "test/inputs/string_input_test.rb" 
> "test/inputs/text_input_test.rb" "test/simple_form_test.rb" -v
> Run options: -v --seed 10076
> 
> # Running:
> 
> PriorityInputTest#test_input_generates_a_country_select_field = 0.00 s = S
> PriorityInputTest#test_input_generates_a_time_zone_select_field_with_default 
> = 0.01 s = E
> PriorityInputTest#test_priority_input_does_not_generate_invalid_aria-required_html_attribute
>  = 0.00 s = S
> PriorityInputTest#test_input_generates_a_time_zone_select_field = 0.00 s = E
> PriorityInputTest#test_input_generates_a_time_zone_select_using_options_priority
>  = 0.00 s = E
> PriorityInputTest#test_priority_input_does_not_generate_invalid_required_html_attribute
>  = 0.00 s = S
> PriorityInputTest#test_input_generates_a_country_select_with_SimpleForm_default
>  = 0.00 s = S
> IsolatedLabelTest#test_label_does_correct_i18n_lookup_for_nested_has_many_models_with_no_nested_translation
>  = 0.01 s = .
> IsolatedLabelTest#test_label_uses_default_input_id_when_it_was_not_overridden 
> = 0.00 s = .
> IsolatedLabelTest#test_label_uses_human_attribute_name_based_on_association_name
>  = 0.00 s = .
> IsolatedLabelTest#test_label_adds_required_by_default_when_object_is_not_present
>  = 0.00 s = .
> IsolatedLabelTest#test_label_does_not_have_css_class_from_type_when_generate_additional_classes_for_does_not_include_:label
>  = 0.00 s = .
> IsolatedLabelTest#test_label_has_css_class_from_type = 0.00 s = .
> 

Bug#839412: marked as done (ruby-tzinfo should depend on tzdata)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-tzinfo should depend on tzdata
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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-leaflet-rails
Version: 0.7.7-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> Invalid gemspec in [leaflet-rails.gemspec]: No such file or directory - git
> GEM_PATH=debian/ruby-leaflet-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"leaflet-rails\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=debian/ruby-leaflet-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation
> config.eager_load is set to nil. Please update your config/environments/*.rb 
> files accordingly:
> 
>   * development - set it to false
>   * test - set it to false (unless you use a tool that preloads your test 
> environment)
>   * production - set it to true
> 
> /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:182:in `rescue in 
> create_default_data_source': No source of timezone data could be found. 
> (TZInfo::DataSourceNotFound)
> Please refer to http://tzinfo.github.io/datasourcenotfound for help resolving 
> this error.
>   from /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:179:in 
> `create_default_data_source'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:40:in `block in 
> get'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:39:in `synchronize'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:39:in `get'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:629:in `data_source'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:92:in `get'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone_proxy.rb:67:in 
> `real_timezone'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone_proxy.rb:30:in 
> `period_for_utc'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:549:in 
> `current_period'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:281:in 
> `utc_offset'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in `block in 
> []'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in `tap'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in `[]'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/core_ext/time/zones.rb:61:in 
> `find_zone!'
>   from /usr/lib/ruby/vendor_ruby/active_support/railtie.rb:20:in `block 
> in '
>   from /usr/lib/ruby/vendor_ruby/rails/initializable.rb:30:in 
> `instance_exec'
>   from /usr/lib/ruby/vendor_ruby/rails/initializable.rb:30:in `run'
>   from /usr/lib/ruby/vendor_ruby/rails/initializable.rb:55:in `block in 
> run_initializers'
>   from /usr/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
>   from /usr/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in 
> each_strongly_connected_component'
>   from /usr/lib/ruby/2.3.0/tsort.rb:431:in 
> `each_strongly_connected_component_from'
>   from /usr/lib/ruby/2.3.0/tsort.rb:349:in `block in 
> each_strongly_connected_component'
>   from /usr/lib/ruby/2.3.0/tsort.rb:347:in `each'
>   from /usr/lib/ruby/2.3.0/tsort.rb:347:in `call'
>   from /usr/lib/ruby/2.3.0/tsort.rb:347:in 
> `each_strongly_connected_component'
>   from /usr/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
>   from /usr/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
>   from /usr/lib/ruby/vendor_ruby/rails/initializable.rb:54:in 
> `run_initializers'

Bug#839410: marked as done (ruby-tzinfo should depend on tzdata)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-tzinfo should depend on tzdata
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.)


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

Hi,

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

Relevant part (hopefully):
> Invalid gemspec in [enumerize.gemspec]: No such file or directory - git
> 
> ┌──┐
> │ Install files   
>  │
> └──┘
> 
> install -d /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby
> install -D -m644 /<>/lib/enumerize.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize.rb
> install -D -m644 /<>/lib/enumerize/module_attributes.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/module_attributes.rb
> install -D -m644 /<>/lib/enumerize/attribute_map.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/attribute_map.rb
> install -D -m644 /<>/lib/enumerize/set.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/set.rb
> install -D -m644 /<>/lib/enumerize/mongoid.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/mongoid.rb
> install -D -m644 /<>/lib/enumerize/predicates.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/predicates.rb
> install -D -m644 /<>/lib/enumerize/attribute.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/attribute.rb
> install -D -m644 /<>/lib/enumerize/predicatable.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/predicatable.rb
> install -D -m644 /<>/lib/enumerize/integrations/rspec/matcher.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/integrations/rspec/matcher.rb
> install -D -m644 /<>/lib/enumerize/integrations/rspec.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/integrations/rspec.rb
> install -D -m644 /<>/lib/enumerize/integrations/rails_admin.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/integrations/rails_admin.rb
> install -D -m644 /<>/lib/enumerize/base.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/base.rb
> install -D -m644 /<>/lib/enumerize/module.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/module.rb
> install -D -m644 /<>/lib/enumerize/hooks/formtastic.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/hooks/formtastic.rb
> install -D -m644 /<>/lib/enumerize/hooks/simple_form.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/hooks/simple_form.rb
> install -D -m644 /<>/lib/enumerize/hooks/uniqueness.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/hooks/uniqueness.rb
> install -D -m644 /<>/lib/enumerize/hooks/sequel_dataset.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/hooks/sequel_dataset.rb
> install -D -m644 /<>/lib/enumerize/version.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/version.rb
> install -D -m644 /<>/lib/enumerize/value.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/value.rb
> install -D -m644 /<>/lib/enumerize/sequel.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/sequel.rb
> install -D -m644 /<>/lib/enumerize/scope/mongoid.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/scope/mongoid.rb
> install -D -m644 /<>/lib/enumerize/scope/sequel.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/scope/sequel.rb
> install -D -m644 /<>/lib/enumerize/scope/activerecord.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/scope/activerecord.rb
> install -D -m644 /<>/lib/enumerize/activerecord.rb 
> /<>/debian/ruby-enumerize/usr/lib/ruby/vendor_ruby/enumerize/activerecord.rb
> dh_installchangelogs -pruby-enumerize /<>/CHANGELOG.md upstream
> 
> ┌──┐
> │ Install Rubygems integration metadata   
>  │
> 

Bug#839456: marked as done (ruby-tzinfo should depend on tzdata)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-tzinfo should depend on tzdata
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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sentry-raven
Version: 1.1.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: TestApp.initialize!
> 
>  TZInfo::DataSourceNotFound:
>No source of timezone data could be found.
>Please refer to http://tzinfo.github.io/datasourcenotfound for help 
> resolving this error.
>  # ./spec/raven/integrations/rails_spec.rb:13:in `block (2 levels) in 
> '
>  # --
>  # --- Caused by: ---
>  # TZInfo::ZoneinfoDirectoryNotFound:
>  #   None of the paths included in TZInfo::ZoneinfoDataSource.search_path 
> are valid zoneinfo directories.
>  #   ./spec/raven/integrations/rails_spec.rb:13:in `block (2 levels) in 
> '
> 
> Finished in 0.69628 seconds (files took 0.77116 seconds to load)
> 218 examples, 6 failures
> 
> Failed examples:
> 
> rspec ./spec/raven/integrations/rails_spec.rb:20 # TestApp inserts middleware
> rspec ./spec/raven/integrations/rails_spec.rb:24 # TestApp should capture 
> exceptions in production
> rspec ./spec/raven/integrations/rails_spec.rb:30 # TestApp should properly 
> set the exception's URL
> rspec ./spec/raven/integrations/rails_spec.rb:40 # TestApp sets 
> Raven.configuration.logger correctly
> rspec ./spec/raven/integrations/rails_spec.rb:44 # TestApp sets 
> Raven.configuration.project_root correctly
> rspec ./spec/raven/integrations/rails_spec.rb:48 # TestApp doesn't clobber a 
> manually configured release
> 
> E, [2016-10-01T11:46:21.610176 #25800] ERROR -- : ** [Raven] Unable to record 
> event with remote Sentry server (Faraday::Adapter::Test::Stubs::NotFound - no 
> stubbed request for post /sentry/api/42/store/ 
> {"event_id":"8178edb61057a91314f44dd6f9d1de3b","message":"SystemExit: 
> exit","timestamp":"2016-10-01T11:46:21","time_spent":null,"level":40,"project":null,"platform":"ruby","logger":"","culprit":"rspec/core/runner.rb
>  in exit at line 
> 46","server_name":"ip-172-31-11-236","modules":{"actionmailer":"4.2.7.1","actionpack":"4.2.7.1","actionview":"4.2.7.1","activejob":"4.2.7.1","activemodel":"4.2.7.1","activerecord":"4.2.7.1","activesupport":"4.2.7.1","arel":"6.0.3","atomic":"1.1.16","bigdecimal":"1.2.8","blankslate":"3.1.3","builder":"3.2.2","bundler":"1.12.5","concurrent-ruby":"1.0.0","did_you_mean":"1.0.0","diff-lcs":"1.2.5","erubis":"2.7.0","faraday":"0.9.2","globalid":"0.3.6","hike":"1.2.1","i18n":"0.7.0","io-console":"0.4.5","json":"1.8.3","loofah":"2.0.3","mail":"2.6.4","mime-types":"2.6.1","minitest":"5.9.0","molinillo":"0.5.0","multi_json":"1.11.2","multipart-post":"1.2.0","net-http-persistent":"2.9.4","net-telnet":"0.1.1","nokogiri":"1.6.8","pkg-config":"1.1.7","polyglot":"0.3.4","power_assert":"0.2.7","psych":"2.0.17","rack":"1.6.4","rack-test":"0.6.3","rails":"4.2.7.1","rails-deprecated_sanitizer":"1.0.3","rails-dom-testing":"1.0.6","rails-html-sanitizer":"1.0.3","railties":"4.2.7.1","rake":"10.5.0","rdoc":"4.2.1","rspec":"3.4.0","rspec-core":"3.4.3","rspec-expectations":"3.4.0","rspec-mocks":"3.4.1","rspec-rails":"3.4.2","rspec-support":"3.4.1","sentry-raven":"1.1.0","sprockets":"3.7.0","sprockets-rails":"2.3.2","test-unit":"3.1.7","thor":"0.19.1","thread_order":"1.1.0","thread_safe":"0.3.5","tilt":"2.0.1","timecop":"0.8.0","treetop":"1.6.3","tzinfo":"1.2.2"},"extra":{},"tags":{},"user":{},"exception":{"values":[{"type":"SystemExit","value":"exit","module":"","stacktrace":{"frames":[{"pre_context":["#!/usr/bin/env
>  ruby\n","\n","require 
> 'rspec/core'\n"],"post_context":[null,null,null],"abs_path":"/usr/bin/rspec","function":"","lineno":4,"in_app":false,"context_line":"RSpec::Core::Runner.invoke\n","project_root":"/<>","filename":"/usr/bin/rspec"},{"pre_context":["
>   def self.invoke\n","disable_autorun!\n","status = 
> run(ARGV, $stderr, $stdout).to_i\n"],"post_context":["  end\n","\n"," 
>  # Run a suite of RSpec examples. Does not 
> 

Bug#839492: marked as done (ruby-delayed-job: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: Time.zone = 'US/Eastern')

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-delayed-job: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: 
Time.zone = 'US/Eastern'
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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-delayed-job
Version: 4.0.6-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: Time.zone = 'US/Eastern'
> 
>  TZInfo::DataSourceNotFound:
>No source of timezone data could be found.
>Please refer to http://tzinfo.github.io/datasourcenotfound for help 
> resolving this error.
>  Shared Example Group: "a delayed_job backend" called from 
> ./spec/test_backend_spec.rb:4
>  # ./lib/delayed/backend/shared_spec.rb:230:in `block (3 levels) in  (required)>'
>  # --
>  # --- Caused by: ---
>  # TZInfo::ZoneinfoDirectoryNotFound:
>  #   None of the paths included in TZInfo::ZoneinfoDataSource.search_path 
> are valid zoneinfo directories.
>  #   ./lib/delayed/backend/shared_spec.rb:230:in `block (3 levels) in 
> '
> 
> Finished in 1.25 seconds (files took 0.96544 seconds to load)
> 148 examples, 1 failure
> 
> Failed examples:
> 
> rspec './spec/test_backend_spec.rb[1:1:7:4]' # Delayed::Backend::Test::Job it 
> should behave like a delayed_job backend reserve reserves jobs scheduled for 
> the past when time zones are involved
> 
> ERROR: Test "ruby2.3" failed: 

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/ruby-delayed-job_4.0.6-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-tzinfo
Source-Version: 1.2.2-2

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

Debian distribution maintenance software
pp.
Hleb Valoshka <375...@gmail.com> (supplier of updated ruby-tzinfo 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: Sun, 02 Oct 2016 10:20:55 +0300
Source: ruby-tzinfo
Binary: ruby-tzinfo
Architecture: source all
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Hleb Valoshka <375...@gmail.com>
Description:
 ruby-tzinfo - Daylight-savings aware timezone library
Closes: 839407
Changes:
 ruby-tzinfo (1.2.2-2) unstable; urgency=medium
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
   * Run wrap-and-sort on packaging files
 .
   [ Hleb Valoshka ]
   * Bump Standards-Version to 3.9.8 (no changes)
   * Add tzdata to dependencies (Closes: #839407)
Checksums-Sha1:
 1973be82a79df795ebe06db21ea5e0649e9fc16a 2029 ruby-tzinfo_1.2.2-2.dsc
 

Bug#839472: marked as done (ruby-tzinfo should depend on tzdata)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-tzinfo should depend on tzdata
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.)


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

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-timecop/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"timecop\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rb 
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-timecop/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/ruby-timecop/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 debian/ruby-tests.rb
> ./test/timecop_without_date_test.rb
> MiniTest::Unit::TestCase is now Minitest::Test. From 
> ./test/timecop_without_date_test.rb:4:in `'
> Run options: --seed 43573
> 
> # Running:
> 
> 
> 
> Finished in 0.502564s, 15.9184 runs/s, 59.6939 assertions/s.
> 
> 8 runs, 30 assertions, 0 failures, 0 errors, 0 skips
> ./test/timecop_without_date_but_with_time_test.rb
> MiniTest::Unit::TestCase is now Minitest::Test. From 
> ./test/timecop_without_date_but_with_time_test.rb:3:in `'
> Run options: --seed 54968
> 
> # Running:
> 
> .
> 
> Finished in 0.007319s, 136.6389 runs/s, 0. assertions/s.
> 
> 1 runs, 0 assertions, 0 failures, 0 errors, 0 skips
> ./test/time_stack_item_test.rb
> MiniTest::Unit::TestCase is now Minitest::Test. From 
> ./test/time_stack_item_test.rb:7:in `'
> Run options: --seed 49857
> 
> # Running:
> 
> E.EE..EEEE.E
> 
> Finished in 0.007295s, 3838.0760 runs/s, 7813.2261 assertions/s.
> 
>   1) Error:
> TestTimeStackItem#test_time_now_always_returns_local_time:
> TZInfo::DataSourceNotFound: No source of timezone data could be found.
> Please refer to http://tzinfo.github.io/datasourcenotfound for help resolving 
> this error.
> /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:182:in `rescue in 
> create_default_data_source'
> /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:179:in 
> `create_default_data_source'
> /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:40:in `block in get'
> /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:39:in `synchronize'
> /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:39:in `get'
> /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:629:in `data_source'
> /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:92:in `get'
> /usr/lib/ruby/vendor_ruby/tzinfo/timezone_proxy.rb:67:in `real_timezone'
> /usr/lib/ruby/vendor_ruby/tzinfo/timezone_proxy.rb:30:in `period_for_utc'
> /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:549:in `current_period'
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:281:in 
> `utc_offset'
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in 
> `block in []'
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in `tap'
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in `[]'
> /usr/lib/ruby/vendor_ruby/active_support/core_ext/time/zones.rb:61:in 
> `find_zone!'
> /usr/lib/ruby/vendor_ruby/active_support/core_ext/time/zones.rb:40:in 
> `zone='
> ./test/time_stack_item_test.rb:232:in 
> `test_time_now_always_returns_local_time'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in 
> run'
> /usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
> 

Bug#839494: marked as done (ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: Combustion::Application.initialize!)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-combustion: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: 
Combustion::Application.initialize!
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.)


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

Hi,

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

Relevant part (hopefully):
>  Failure/Error: Combustion::Application.initialize!
> 
>  TZInfo::DataSourceNotFound:
>No source of timezone data could be found.
>Please refer to http://tzinfo.github.io/datasourcenotfound for help 
> resolving this error.
>  # ./lib/combustion.rb:34:in `initialize!'
>  # ./spec/database_spec.rb:8:in `block (3 levels) in '
>  # ./spec/database_spec.rb:7:in `chdir'
>  # ./spec/database_spec.rb:7:in `block (2 levels) in '
>  # --
>  # --- Caused by: ---
>  # TZInfo::ZoneinfoDirectoryNotFound:
>  #   None of the paths included in TZInfo::ZoneinfoDataSource.search_path 
> are valid zoneinfo directories.
>  #   ./lib/combustion.rb:34:in `initialize!'
> 
> Finished in 0.23716 seconds (files took 0.56632 seconds to load)
> 1 example, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/database_spec.rb:12 # Combustion::Database run migration from 
> dummy engine
> 
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*_spec.rb failed
> ERROR: Test "ruby2.3" failed: 

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/01/ruby-combustion_0.5.4-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-tzinfo
Source-Version: 1.2.2-2

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

Debian distribution maintenance software
pp.
Hleb Valoshka <375...@gmail.com> (supplier of updated ruby-tzinfo 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: Sun, 02 Oct 2016 10:20:55 +0300
Source: ruby-tzinfo
Binary: ruby-tzinfo
Architecture: source all
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Hleb Valoshka <375...@gmail.com>
Description:
 ruby-tzinfo - Daylight-savings aware timezone library
Closes: 839407
Changes:
 ruby-tzinfo (1.2.2-2) unstable; urgency=medium
 .
   [ Cédric Boutillier ]
   * Bump debhelper compatibility level to 9
   * Remove version in the gem2deb build-dependency
   * Use https:// in Vcs-* fields
   * Run wrap-and-sort on packaging files
 .
   [ Hleb Valoshka ]
   * Bump Standards-Version to 3.9.8 (no changes)
   * Add tzdata to dependencies (Closes: #839407)
Checksums-Sha1:
 1973be82a79df795ebe06db21ea5e0649e9fc16a 2029 ruby-tzinfo_1.2.2-2.dsc
 

Bug#839407: marked as done (ruby-tzinfo should depend on tzdata)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-tzinfo should depend on tzdata
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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: samizdat
Version: 0.7.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-test-files.yaml  
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/samizdat/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ 
> \{\ \|f\|\ require\ f\ \}
> Loaded suite -e
> Started
> E
> ===
> Error: test_box_with_title(TC_ApplicationHelper):
>   TZInfo::DataSourceNotFound: No source of timezone data could be found.
>   Please refer to http://tzinfo.github.io/datasourcenotfound for help 
> resolving this error.
> /<>/test/mock.rb:46:in `initialize'
> /usr/lib/ruby/2.3.0/singleton.rb:142:in `new'
> /usr/lib/ruby/2.3.0/singleton.rb:142:in `block in instance'
> /usr/lib/ruby/2.3.0/singleton.rb:140:in `synchronize'
> /usr/lib/ruby/2.3.0/singleton.rb:140:in `instance'
> /<>/test/mock.rb:83:in `initialize'
> /<>/test/tc_application_helper.rb:27:in `new'
> /<>/test/tc_application_helper.rb:27:in `setup'
> ===
> E
> ===
> Error: test_box_without_title(TC_ApplicationHelper):
>   TZInfo::DataSourceNotFound: No source of timezone data could be found.
>   Please refer to http://tzinfo.github.io/datasourcenotfound for help 
> resolving this error.
> /<>/test/mock.rb:46:in `initialize'
> /usr/lib/ruby/2.3.0/singleton.rb:142:in `new'
> /usr/lib/ruby/2.3.0/singleton.rb:142:in `block in instance'
> /usr/lib/ruby/2.3.0/singleton.rb:140:in `synchronize'
> /usr/lib/ruby/2.3.0/singleton.rb:140:in `instance'
> /<>/test/mock.rb:83:in `initialize'
> /<>/test/tc_application_helper.rb:27:in `new'
> /<>/test/tc_application_helper.rb:27:in `setup'
> ===
> E
> ===
> Error: test_form(TC_ApplicationHelper):
>   TZInfo::DataSourceNotFound: No source of timezone data could be found.
>   Please refer to http://tzinfo.github.io/datasourcenotfound for help 
> resolving this error.
> /<>/test/mock.rb:46:in `initialize'
> /usr/lib/ruby/2.3.0/singleton.rb:142:in `new'
> /usr/lib/ruby/2.3.0/singleton.rb:142:in `block in instance'
> /usr/lib/ruby/2.3.0/singleton.rb:140:in `synchronize'
> /usr/lib/ruby/2.3.0/singleton.rb:140:in `instance'
> /<>/test/mock.rb:83:in `initialize'
> /<>/test/tc_application_helper.rb:27:in `new'
> /<>/test/tc_application_helper.rb:27:in `setup'
> ===
> E
> ===
> Error: test_form_field_input(TC_ApplicationHelper):
>   TZInfo::DataSourceNotFound: No source of timezone data could be found.
>   Please refer to http://tzinfo.github.io/datasourcenotfound for help 
> resolving this error.
> /<>/test/mock.rb:46:in `initialize'
> /usr/lib/ruby/2.3.0/singleton.rb:142:in `new'
> /usr/lib/ruby/2.3.0/singleton.rb:142:in `block in instance'
> /usr/lib/ruby/2.3.0/singleton.rb:140:in `synchronize'
> /usr/lib/ruby/2.3.0/singleton.rb:140:in `instance'
> /<>/test/mock.rb:83:in `initialize'
> /<>/test/tc_application_helper.rb:27:in `new'
> /<>/test/tc_application_helper.rb:27:in `setup'
> ===
> E
> 

Bug#839525: marked as done (ruby-active-model-serializers: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-active-model-serializers: FTBFS: ERROR: Test "ruby2.3" 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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-active-model-serializers
Version: 0.9.5-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=debian/ruby-active-model-serializers/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/integration/action_controller/namespaced_serialization_test.rb" 
> "test/integration/action_controller/serialization_test.rb" 
> "test/integration/action_controller/serialization_test_case_test.rb" 
> "test/integration/active_record/active_record_test.rb" 
> "test/integration/generators/resource_generator_test.rb" 
> "test/integration/generators/scaffold_controller_generator_test.rb" 
> "test/integration/generators/serializer_generator_test.rb" 
> "test/unit/active_model/array_serializer/except_test.rb" 
> "test/unit/active_model/array_serializer/key_format_test.rb" 
> "test/unit/active_model/array_serializer/meta_test.rb" 
> "test/unit/active_model/array_serializer/only_test.rb" 
> "test/unit/active_model/array_serializer/options_test.rb" 
> "test/unit/active_model/array_serializer/root_test.rb" 
> "test/unit/active_model/array_serializer/scope_test.rb" 
> "test/unit/active_model/array_serializer/serialization_test.rb" 
> "test/unit/active_model/default_serializer_test.rb" 
> "test/unit/active_model/serializer/associations/build_serializer_test.rb" 
> "test/unit/active_model/serializer/associations_test.rb" 
> "test/unit/active_model/serializer/attributes_test.rb" 
> "test/unit/active_model/serializer/config_test.rb" 
> "test/unit/active_model/serializer/filter_test.rb" 
> "test/unit/active_model/serializer/has_many_polymorphic_test.rb" 
> "test/unit/active_model/serializer/has_many_test.rb" 
> "test/unit/active_model/serializer/has_one_and_has_many_test.rb" 
> "test/unit/active_model/serializer/has_one_polymorphic_test.rb" 
> "test/unit/active_model/serializer/has_one_test.rb" 
> "test/unit/active_model/serializer/key_format_test.rb" 
> "test/unit/active_model/serializer/meta_test.rb" 
> "test/unit/active_model/serializer/options_test.rb" 
> "test/unit/active_model/serializer/root_test.rb" 
> "test/unit/active_model/serializer/scope_test.rb" 
> "test/unit/active_model/serializer/url_helpers_test.rb" -v
> DEPRECATION WARNING: ** Notice: include was renamed to embed_in_root. **
> . (called from initialize at 
> /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/association.rb:10)
> DEPRECATION WARNING: ** Notice: include was renamed to embed_in_root. **
> . (called from initialize at 
> /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/association.rb:10)
> DEPRECATION WARNING: ** Notice: include was renamed to embed_in_root. **
> . (called from initialize at 
> /<>/debian/ruby-active-model-serializers/usr/lib/ruby/vendor_ruby/active_model/serializer/association.rb:10)
> DEPRECATION WARNING: `#timestamps` was called without specifying an option 
> for `null`. In Rails 5, this behavior will change to `null: false`. You 
> should manually specify `null: true` to prevent the behavior of your existing 
> migrations from changing. (called from block (2 levels) in  
> at /<>/test/fixtures/active_record.rb:13)
> DEPRECATION WARNING: `#timestamps` was called without specifying an option 
> for `null`. In Rails 5, this behavior will change 

Bug#805962: marked as done (witty: FTBFS when built with dpkg-buildpackage -A (no binary artifacts))

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:43 +
with message-id 
and subject line Bug#805962: fixed in witty 3.3.5+dfsg-1.1
has caused the Debian Bug report #805962,
regarding witty: FTBFS when built with dpkg-buildpackage -A (no binary 
artifacts)
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.)


-- 
805962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:witty
Version: 3.3.4+dfsg-6
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
dh_clean -k 
dh_clean: dh_clean -k is deprecated; use dh_prep instead
dh_installdirs
# Commands to install the package into debian/tmp

[ ... snipped ... ]

patch -p1 -d debian/tmp/usr/lib/Wt < 
debian/patches/07_tests_cmake_dependencies.dpatch
patching file test/CMakeLists.txt
rm 
/<>/witty-3.3.4+dfsg/debian/tmp/usr/lib/Wt/examples/wtwithqt/LICENSE
rm 
/<>/witty-3.3.4+dfsg/debian/tmp/usr/lib/Wt/examples/wtwithqt/lib/LICENSE
 dpkg-genchanges -A >../witty_3.3.4+dfsg-6_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


This usually happens because there is a binary-indep target in debian/rules
which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released 
with jessie,
the easy fix is to drop them now. If not, debian/rules should be modified so 
that the
binary-indep target generates the architecture independent packages (and only 
those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if 
you wish
(I recommend that you try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: witty
Source-Version: 3.3.5+dfsg-1.1

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated witty 
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: Mon, 03 Oct 2016 09:47:19 +0200
Source: witty
Binary: libwt-common libwt39 libwt-dev libwthttp39 libwthttp-dev libwtfcgi39 
libwtfcgi-dev libwttest9 libwttest-dev libwtext39 libwtext-dev libwtdbo39 
libwtdbo-dev libwtdbosqlite39 libwtdbosqlite-dev libwtdbopostgres39 
libwtdbopostgres-dev libwtdbofirebird39 libwtdbofirebird-dev libwtdbomysql39 
libwtdbomysql-dev libwt-dbg libwt-doc witty-examples witty witty-dbg witty-dev 
witty-doc
Architecture: source
Version: 3.3.5+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Pau Garcia i Quiles 
Changed-By: Gianfranco Costamagna 
Description:
 libwt-common - C++ library and application server for web applications [common]
 libwt-dbg  - C++ library and application server for web applications [debug]
 libwt-dev  - C++ library and application server for web applications [developm
 libwt-doc  - C++ library and application server for web applications [doc]
 libwt39- C++ library and application server for web applications [runtime]
 libwtdbo-dev - Wt::Dbo ORM library for Wt [development]
 libwtdbo39 - Wt::Dbo ORM library for Wt [runtime]
 libwtdbofirebird-dev - Firebird backend for Wt::Dbo [development]
 libwtdbofirebird39 - Firebird backend for Wt::Dbo [runtime]
 libwtdbomysql-dev - MySQL/MariaDB backend for Wt::Dbo [development]
 libwtdbomysql39 - MySQL/MariaDB backend for Wt::Dbo [runtime]
 libwtdbopostgres-dev - PostgreSQL backend for Wt::Dbo [development]
 libwtdbopostgres39 

Bug#839495: marked as done (ruby-globalid: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-globalid: FTBFS: ERROR: Test "ruby2.3" 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.)


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

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-globalid/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"globalid\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-globalid/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/ruby-globalid/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
> "test/cases/global_id_test.rb" "test/cases/global_identification_test.rb" 
> "test/cases/global_locator_test.rb" "test/cases/railtie_test.rb" 
> "test/cases/signed_global_id_test.rb" "test/cases/uri_gid_test.rb" -v
> Run options: -v --seed 3261
> 
> # Running:
> 
> URI::GIDTest#test_build = 0.00 s = .
> URI::GIDTest#test_as_String = 0.00 s = .
> URI::GIDTest#test_build_with_wrong_ordered_array_creates_a_wrong_ordered_gid 
> = 0.00 s = .
> URI::GIDTest#test_equal = 0.00 s = .
> URI::GIDTest#test_parsed = 0.00 s = .
> URI::GIDTest#test_create = 0.00 s = .
> URI::GIDTest#test_new_returns_invalid_gid_when_not_checking = 0.00 s = .
> GlobalIDParamEncodedTest#test_finding = 0.00 s = .
> GlobalIDParamEncodedTest#test_parsing = 0.00 s = .
> URI::GIDModelIDEncodingTest#test_alphanumeric = 0.00 s = .
> URI::GIDModelIDEncodingTest#test_non-alphanumeric = 0.00 s = .
> URI::GIDValidationTest#test_too_many_model_ids = 0.00 s = .
> URI::GIDValidationTest#test_missing_model_id = 0.00 s = .
> URI::GIDValidationTest#test_invalid_schemes = 0.00 s = .
> URI::GIDValidationTest#test_missing_path = 0.00 s = .
> URI::GIDValidationTest#test_empty = 0.00 s = .
> URI::GIDValidationTest#test_missing_app = 0.00 s = .
> SignedGlobalIDExpirationTest#test_favor_expires_at_over_expires_in = 0.00 s = 
> .
> SignedGlobalIDExpirationTest#test_expires_in_defaults_to_class_level_expiration
>  = 0.00 s = .
> SignedGlobalIDExpirationTest#test_passing_expires_at_sets_expiration_date = 
> 0.00 s = .
> SignedGlobalIDExpirationTest#test_passing_expires_in_less_than_a_second_is_not_expired
>  = 0.00 s = .
> SignedGlobalIDExpirationTest#test_passing_in_expires_in_overrides_class_level_expiration
>  = 0.00 s = .
> SignedGlobalIDExpirationTest#test_passing_nil_expires_at_turns_off_expiration_checking
>  = 0.00 s = .
> SignedGlobalIDExpirationTest#test_passing_expires_at_overrides_class_level_expires_in
>  = 0.00 s = .
> SignedGlobalIDExpirationTest#test_passing_expires_in_nil_turns_off_expiration_checking
>  = 0.00 s = .
> ScopedRecordLocatingTest#test_by_GID_with_scoped_record = 0.00 s = .
> ScopedRecordLocatingTest#test_by_many_with_scoped_records = 0.00 s = .
> SignedGlobalIDVerifierTest#test_new_accepts_a_:verifier = 0.00 s = .
> SignedGlobalIDVerifierTest#test_parse_raises_when_default_verifier_is_nil = 
> 0.00 s = .
> SignedGlobalIDVerifierTest#test_create_accepts_a_:verifier = 0.00 s = .
> SignedGlobalIDVerifierTest#test_create_raises_when_default_verifier_is_nil = 
> 0.00 s = .
> URI::GIDModelIDDecodingTest#test_alphanumeric = 0.00 s = .
> URI::GIDModelIDDecodingTest#test_non-alphanumeric = 0.00 s = .
> 

Bug#839500: marked as done (ruby-simple-navigation: FTBFS: ERROR: Test "ruby2.3" failed.)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-simple-navigation: FTBFS: ERROR: Test "ruby2.3" 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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-simple-navigation
Version: 4.0.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-simple-navigation/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"simple-navigation\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-simple-navigation/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=debian/ruby-simple-navigation/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
> documentation
> /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:182:in `rescue in 
> create_default_data_source': No source of timezone data could be found. 
> (TZInfo::DataSourceNotFound)
> Please refer to http://tzinfo.github.io/datasourcenotfound for help resolving 
> this error.
>   from /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:179:in 
> `create_default_data_source'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:40:in `block in 
> get'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:39:in `synchronize'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:39:in `get'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:629:in `data_source'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:92:in `get'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone_proxy.rb:67:in 
> `real_timezone'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone_proxy.rb:30:in 
> `period_for_utc'
>   from /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:549:in 
> `current_period'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:281:in 
> `utc_offset'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in `block in 
> []'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in `tap'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in `[]'
>   from 
> /usr/lib/ruby/vendor_ruby/active_support/core_ext/time/zones.rb:61:in 
> `find_zone!'
>   from /usr/lib/ruby/vendor_ruby/active_support/railtie.rb:20:in `block 
> in '
>   from /usr/lib/ruby/vendor_ruby/rails/initializable.rb:30:in 
> `instance_exec'
>   from /usr/lib/ruby/vendor_ruby/rails/initializable.rb:30:in `run'
>   from /usr/lib/ruby/vendor_ruby/rails/initializable.rb:55:in `block in 
> run_initializers'
>   from /usr/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
>   from /usr/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in 
> each_strongly_connected_component'
>   from /usr/lib/ruby/2.3.0/tsort.rb:431:in 
> `each_strongly_connected_component_from'
>   from /usr/lib/ruby/2.3.0/tsort.rb:349:in `block in 
> each_strongly_connected_component'
>   from /usr/lib/ruby/2.3.0/tsort.rb:347:in `each'
>   from /usr/lib/ruby/2.3.0/tsort.rb:347:in `call'
>   from /usr/lib/ruby/2.3.0/tsort.rb:347:in 
> `each_strongly_connected_component'
>   from /usr/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
>   from /usr/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
>   from 

Bug#839465: marked as done (ruby-tzinfo should depend on tzdata)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-tzinfo should depend on tzdata
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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-clockwork
Version: 1.2.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.3  
>  │
> └──┘
> 
> GEM_PATH=debian/ruby-clockwork/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -e gem\ \"clockwork\"
> 
> ┌──┐
> │ Run tests for ruby2.3 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-clockwork/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=debian/ruby-clockwork/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
>  ruby2.3 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby2.3 -I"test"  
> "/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/at_test.rb" 
> "test/clockwork_test.rb" "test/database_events/sync_performer_test.rb" 
> "test/event_test.rb" "test/manager_test.rb" 
> "test/database_events/test_helpers.rb" -v
> 
> *** Mocha deprecation warning: Test::Unit or MiniTest must be loaded *before* 
> `require 'mocha/setup'`.
> 
> 
> *** Mocha deprecation warning: If you're integrating with a test library 
> other than Test::Unit or MiniTest, you should use `require 'mocha/api'` 
> instead of `require 'mocha/setup'`.
> 
> Run options: -v --seed 39490
> 
> # Running:
> 
> Clockwork::At#test_0002_8:20 = 0.00 s = .
> Clockwork::At#test_0005_16:** = 0.00 s = .
> Clockwork::At#test_0009_invalid time 32:00 = 0.00 s = .
> Clockwork::At#test_0012_invalid multi-line with *:10 = 0.00 s = .
> Clockwork::At#test_0003_**:20 with two stars = 0.00 s = .
> Clockwork::At#test_0011_invalid multi-line with 8:30 = 0.00 s = .
> Clockwork::At#test_0007_Saturday 12:00 = 0.00 s = .
> Clockwork::At#test_0010_invalid multi-line with Sat 12:00 = 0.00 s = .
> Clockwork::At#test_0004_*:20 with one star = 0.00 s = .
> Clockwork::At#test_0008_sat 12:00 = 0.00 s = .
> Clockwork::At#test_0001_16:20 = 0.00 s = .
> Clockwork::At#test_0013_invalid multi-line with 12:** = 0.00 s = .
> Clockwork::At#test_0006_8:** = 0.00 s = .
> Clockwork::Manager:::if option#test_0001_:if true then always run = 0.00 s = .
> Clockwork::Manager:::if option#test_0003_:if the first day of month = 0.00 s 
> = .
> Clockwork::Manager:::if option#test_0004_:if it is compared to a time with 
> zone = 0.00 s = E
> Clockwork::Manager:::if option#test_0002_:if false then never run = 0.00 s = .
> Clockwork::Manager:::if option#test_0005_:if is not callable then raise 
> ArgumentError = 0.00 s = .
> Clockwork::Manager:::at option#test_0001_once a day at 16:20 = 0.00 s = .
> Clockwork::Manager:::at option#test_0002_twice a day at 16:20 and 18:10 = 
> 0.00 s = .
> Clockwork::Manager::error_handler#test_0002_error is notified to logger and 
> handler = 0.00 s = .
> Clockwork::Manager::error_handler#test_0001_registered error_handler handles 
> error from event = 0.00 s = .
> Clockwork::Manager::error_handler#test_0003_error in handler will NOT be 
> suppressed = 0.00 s = .
> Clockwork::DatabaseEvents::SyncPerformer::setup::when database reload 
> frequency is less than model frequency period#test_0001_runs event only once 
> within the model frequency period = 0.00 s = .
> Clockwork::Manager::callbacks#test_0003_should not run events if before_tick 
> returns false = 0.00 s = .
> Clockwork::Manager::callbacks#test_0006_should run after_run callback for 
> each event = 0.00 s = .
> 

Bug#839479: marked as done (ruby-tzinfo should depend on tzdata)

[Debian Bug Tracking System]

Your message dated Mon, 03 Oct 2016 09:53:04 +
with message-id 
and subject line Bug#839407: fixed in ruby-tzinfo 1.2.2-2
has caused the Debian Bug report #839407,
regarding ruby-tzinfo should depend on tzdata
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.)


-- 
839407: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-delayed-job-active-record
Version: 4.0.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161001 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
>  Failure/Error: raise DataSourceNotFound, "No source of timezone data 
> could be found.\nPlease refer to http://tzinfo.github.io/datasourcenotfound 
> for help resolving this error."
> 
>  TZInfo::DataSourceNotFound:
>No source of timezone data could be found.
>Please refer to http://tzinfo.github.io/datasourcenotfound for help 
> resolving this error.
>  Shared Example Group: "a delayed_job backend" called from 
> ./spec/delayed/backend/active_record_spec.rb:5
>  # /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:182:in `rescue in 
> create_default_data_source'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:179:in 
> `create_default_data_source'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:40:in `block in get'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:39:in `synchronize'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/data_source.rb:39:in `get'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:629:in `data_source'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:92:in `get'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/timezone_proxy.rb:67:in 
> `real_timezone'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/timezone_proxy.rb:30:in 
> `period_for_utc'
>  # /usr/lib/ruby/vendor_ruby/tzinfo/timezone.rb:549:in `current_period'
>  # /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:281:in 
> `utc_offset'
>  # /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in 
> `block in []'
>  # /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in 
> `tap'
>  # /usr/lib/ruby/vendor_ruby/active_support/values/time_zone.rb:243:in 
> `[]'
>  # /usr/lib/ruby/vendor_ruby/active_support/core_ext/time/zones.rb:61:in 
> `find_zone!'
>  # /usr/lib/ruby/vendor_ruby/active_support/core_ext/time/zones.rb:40:in 
> `zone='
>  # /usr/lib/ruby/vendor_ruby/delayed/backend/shared_spec.rb:230:in `block 
> (3 levels) in '
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:236:in `instance_exec'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:236:in `block in run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:478:in `block in 
> with_around_and_singleton_context_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:435:in `block in 
> with_around_example_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:478:in `block in run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:616:in 
> `run_around_example_hooks_for'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/hooks.rb:478:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:435:in 
> `with_around_example_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:478:in 
> `with_around_and_singleton_context_hooks'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example.rb:233:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:581:in `block in 
> run_examples'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:577:in `map'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:577:in 
> `run_examples'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:543:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:544:in `block in 
> run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:544:in `map'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:544:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:544:in `block in 
> run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:544:in `map'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/example_group.rb:544:in `run'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:119:in `block (3 
> levels) in run_specs'
>  # /usr/lib/ruby/vendor_ruby/rspec/core/runner.rb:119:in `map'
>  #