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

2016-10-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 839444 serious Bug #839444 [src:libgda5] libgda5: FTBFS: tests failures annotations: Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 839444: http://bugs.debian.o

Bug#832531: marked as done (namazu2: FTBFS (No such file or directory))

2016-10-03 Thread Debian Bug Tracking System
Your message dated Tue, 04 Oct 2016 06:33:37 + with message-id and subject line Bug#832531: fixed in namazu2 2.0.21-19 has caused the Debian Bug report #832531, regarding namazu2: FTBFS (No such file or directory) to be marked as done. This means that you claim that the problem has been dealt

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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.o

Bug#839567: rake does not work with jruby

2016-10-03 Thread 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.

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

2016-10-03 Thread 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

Processed: your mail

2016-10-03 Thread 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

Processed: tagging 839159

2016-10-03 Thread 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. --

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

2016-10-03 Thread 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 prob

Processed: severity of 839159 is important

2016-10-03 Thread 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:

Processed: just upgrade to new upstream

2016-10-03 Thread 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.debi

Bug#822369: just upgrade to new upstream

2016-10-03 Thread 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

Bug#839567: rake does not work with jruby

2016-10-03 Thread 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 requ

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

2016-10-03 Thread 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 th

Bug#839567: rake does not work with jruby

2016-10-03 Thread 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 spe

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

2016-10-03 Thread 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

2016-10-03 Thread 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 amd6

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

2016-10-03 Thread 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.

Bug#839010: reopen bug

2016-10-03 Thread 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 bu

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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. :(

Processed: tagging 826192

2016-10-03 Thread 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?bu

Bug#839294: rawdog: FTBFS: Tests failures

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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 b

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

2016-10-03 Thread 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 deal

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

2016-10-03 Thread 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: h

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

2016-10-03 Thread 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

Bug#839567: rake does not work with jruby

2016-10-03 Thread 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 tha

Processed: your mail

2016-10-03 Thread 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

Processed: tagging 831114

2016-10-03 Thread 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 o

Processed: Raise the severity

2016-10-03 Thread 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

Processed: tagging 831114

2016-10-03 Thread 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 o

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

2016-10-03 Thread 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 be

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

2016-10-03 Thread 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 don

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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 bee

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

2016-10-03 Thread 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 si

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

2016-10-03 Thread 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

2016-10-03 Thread 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 o

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

2016-10-03 Thread 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: > >

Processed: tagging 831114

2016-10-03 Thread 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 S

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

2016-10-03 Thread 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: F

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

2016-10-03 Thread 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 i

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

2016-10-03 Thread 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 sto

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

2016-10-03 Thread 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

Processed: [bts-link] source package ghostscript

2016-10-03 Thread 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.debi

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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&revision=22821 > > This new version of the package solv

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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 t

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

2016-10-03 Thread 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 b

Bug#839666: found jessie

2016-10-03 Thread 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

2016-10-03 Thread 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.debia

Bug#839666: Fails to disable uwsgi module upon purge

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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...@b

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

2016-10-03 Thread 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

2016-10-03 Thread 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,

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

2016-10-03 Thread 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: d

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

2016-10-03 Thread 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 tarb

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

2016-10-03 Thread 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 dea

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

2016-10-03 Thread 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 recreat

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

2016-10-03 Thread 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)

2016-10-03 Thread 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

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

2016-10-03 Thread 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 w

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

2016-10-03 Thread 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 s

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

2016-10-03 Thread 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 aut

Processed: found 777525 in 0.10.2-1

2016-10-03 Thread 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' Mar

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

2016-10-03 Thread 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 t

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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 d

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

2016-10-03 Thread 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

Bug#820026: icedove crashes suddenly

2016-10-03 Thread 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...

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)

2016-10-03 Thread 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 don

Bug#811674: fixed in ceph 0.94.5-1.1

2016-10-03 Thread 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. N

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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: Comman

Bug#811674: fixed in ceph 0.94.5-1.1

2016-10-03 Thread 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

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

2016-10-03 Thread 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

Bug#811674: fixed in ceph 0.94.5-1.1

2016-10-03 Thread 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 > affec

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

2016-10-03 Thread 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

2016-10-03 Thread 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

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

2016-10-03 Thread 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 fixe

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

2016-10-03 Thread 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. -- 71

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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. Th

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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 pr

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

2016-10-03 Thread 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

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

2016-10-03 Thread 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

  1   2   >