Bug#830348: marked as pending

tag 830348 pending thanks Hello, Bug #830348 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=openstack/python-pint.git;a=commitdiff;h=e6bbb20 --- commit

Bug#830612: marked as done (python-werkzeug: accesses the internet during build)

Your message dated Mon, 11 Jul 2016 05:48:24 + with message-id and subject line Bug#830612: fixed in python-werkzeug 0.11.10+dfsg1-2 has caused the Debian Bug report #830612, regarding python-werkzeug: accesses the internet during build to be marked as

Processed: Bug#830348 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 830348 pending Bug #830348 [src:python-pint] python-pint: FTBFS: Tests failures Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 830348:

Processed: Bug#830733 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 830733 pending Bug #830733 [src:procps] procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.00 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 830733:

Bug#830733: marked as pending

tag 830733 pending thanks Hello, Bug #830733 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=collab-maint/procps.git;a=commitdiff;h=046a363 --- commit

Bug#812041: marked as done (thrift-compiler: FTBFS with GCC 6: operands to ?: have different)

Your message dated Mon, 11 Jul 2016 05:33:27 + with message-id and subject line Bug#812041: fixed in thrift-compiler 0.9.1-2.1 has caused the Debian Bug report #812041, regarding thrift-compiler: FTBFS with GCC 6: operands to ?: have different to be marked

Bug#643804: marked as done (listen: fails to start)

Your message dated Sun, 10 Jul 2016 15:54:11 +0200 with message-id <15d4d566-2124-6f32-5930-03deaa673...@debian.org> and subject line listen has been removed from Debian in 2012 has caused the Debian Bug report #643804, regarding listen: fails to start to be marked as done. This means that you

Bug#569410: marked as done (multisync0.90: FTBFS: Nonexistent build-dependency: libopensync0-dev)

Your message dated Sun, 10 Jul 2016 13:25:26 +0200 with message-id <2a6ba5e5-9faa-bd0d-7640-218eec487...@debian.org> and subject line opensync et.al. has been removed from Debian in 2012 has caused the Debian Bug report #569410, regarding multisync0.90: FTBFS: Nonexistent build-dependency:

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 830748 https://github.com/supertuxkart/stk-code/issues/2569 Bug #830748 [supertuxkart] supertuxkart: FTBFS on arm64, mips/mips64/mipsel, ppc64el, s390x Set Bug forwarded-to-address to

Bug#569382: marked as done (libopensync-plugin-kdepim: FTBFS: Nonexistent build-dependency: libopensync0-dev)

Your message dated Sun, 10 Jul 2016 13:25:26 +0200 with message-id <2a6ba5e5-9faa-bd0d-7640-218eec487...@debian.org> and subject line opensync et.al. has been removed from Debian in 2012 has caused the Debian Bug report #569382, regarding libopensync-plugin-kdepim: FTBFS: Nonexistent

Processed: severity of 830700 is grave

Processing commands for cont...@bugs.debian.org: > # adjust severity, is at most grave > severity 830700 grave Bug #830700 [tiff] CVE-2016-5314: tiff: PixarLogDecode() heap-based buffer overflow Severity set to 'grave' from 'critical' > thanks Stopping processing here. Please contact me if you

Bug#830751: supertuxkart-data: contains Ubuntu Font Family fonts

Package: supertuxkart-data Version: 0.9.2-1 Severity: serious Justification: non DFSG file in the source package supertuxkart/0.9.2-1 ships with the following files in the source tarball: data/ttf/Ubuntu-B.ttf data/ttf/Ubuntu-R.ttf ...which get installed into binary package supertuxkart-data:

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

Package: supertuxkart Version: 0.9.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) supertuxkart/0.9.2-1 FTBFS on arm64, mips/mips64/mipsel, ppc64el, and s390x; full build log at [1], and here's the relevant part of the log: [ 9%] Building CXX

Bug#811774: marked as done (sdrangelove: FTBFS with GCC 6: narrowing conversion)

Your message dated Mon, 11 Jul 2016 03:52:52 + with message-id and subject line Bug#811774: fixed in sdrangelove 0.0.1.20150707-2 has caused the Debian Bug report #811774, regarding sdrangelove: FTBFS with GCC 6: narrowing conversion to be marked as done.

Bug#830420: marked as done (csoundqt: FTBFS: src/csoundengine.cpp:1252:33: error: conversion from 'uint64_t {aka long unsigned int}' to 'const QVariant' is ambiguous)

Your message dated Mon, 11 Jul 2016 03:50:00 + with message-id and subject line Bug#830420: fixed in csoundqt 0.9.2.1-3 has caused the Debian Bug report #830420, regarding csoundqt: FTBFS: src/csoundengine.cpp:1252:33: error: conversion from 'uint64_t

Bug#830420: marked as pending

tag 830420 pending thanks Hello, Bug #830420 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=pkg-multimedia/csoundqt.git;a=commitdiff;h=888312d --- commit

Processed: Bug#830420 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 830420 pending Bug #830420 [src:csoundqt] csoundqt: FTBFS: src/csoundengine.cpp:1252:33: error: conversion from 'uint64_t {aka long unsigned int}' to 'const QVariant' is ambiguous Added tag(s) pending. > thanks Stopping processing here.

Bug#830683: Missing dependency on module-udev?

On 10 July 2016 at 17:22, Patrick Winnertz wrote: > > thanks > > I know that this split was done by purpose. However even if the split was > done on purpose, this split shouldn't break existing systems - which > actually happened. > It would be nice if you wouldn't close the

Bug#655822: marked as done (slicer: FTBFS: vtkTcl.h:26:17: fatal error: tcl.h: No such file or directory)

Your message dated Sun, 10 Jul 2016 15:11:58 +0200 with message-id <1087bb0c-11a7-c62a-f264-2497be231...@debian.org> and subject line slicer was removed from Debian in 2013 has caused the Debian Bug report #655822, regarding slicer: FTBFS: vtkTcl.h:26:17: fatal error: tcl.h: No such file or

Bug#705960: marked as done (honeyd: missing build-dependency on python)

Your message dated Sun, 10 Jul 2016 13:32:14 +0200 with message-id <801e9a9c-3c5f-cc03-35de-7738acfb6...@debian.org> and subject line honeyd was removed from Debian in 2013 has caused the Debian Bug report #705960, regarding honeyd: missing build-dependency on python to be marked as done. This

Bug#564867: marked as done (avida: ftbfs with gcc-4.5)

Your message dated Sun, 10 Jul 2016 15:36:32 +0200 with message-id <46408c9d-41cc-7575-a475-189c92645...@debian.org> and subject line avida has been removed from Debian in 2011 has caused the Debian Bug report #564867, regarding avida: ftbfs with gcc-4.5 to be marked as done. This means that you

Bug#830472: postal: FTBFS: smtp.h:28:58: error: 'hash' was not declared in this scope

Package: postal Version: 0.74 Followup-For: Bug #830472 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu yakkety ubuntu-patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Fix FTBFS: - smtp.h: + Qualify std::tr1::hash. +

Bug#830744: flint: FTBFS on *-i386: testsuite timeout

Source: flint Version: 2.5.2-7 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, flint FTBFS on *-i386, the testsuite hangs and the build gets terminated after it reaches the inactivity timeout.

Processed: severity of 830673 is normal

Processing commands for cont...@bugs.debian.org: > severity 830673 normal Bug #830673 [src:golang-github-fluent-fluent-logger-golang] golang-github-fluent-fluent-logger-golang: accesses the internet during build Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please

Processed: severity of 830209 is normal

Processing commands for cont...@bugs.debian.org: > severity 830209 normal Bug #830209 [src:docker-registry] docker-registry: accesses the internet during build Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 830209:

Processed: severity of 830677 is normal

Processing commands for cont...@bugs.debian.org: > severity 830677 normal Bug #830677 [src:golang-github-unknwon-com] golang-github-unknwon-com: accesses the internet during build Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 830674 is normal

Processing commands for cont...@bugs.debian.org: > severity 830674 normal Bug #830674 [src:golang-github-franela-goreq] golang-github-franela-goreq: accesses the internet during build Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 830676 is normal

Processing commands for cont...@bugs.debian.org: > severity 830676 normal Bug #830676 [src:golang-github-shopify-sarama] golang-github-shopify-sarama: accesses the internet during build Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 830678 is normal

Processing commands for cont...@bugs.debian.org: > severity 830678 normal Bug #830678 [src:golang-github-xeipuuv-gojsonschema] golang-github-xeipuuv-gojsonschema: accesses the internet during build Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if

Processed: severity of 830675 is normal

Processing commands for cont...@bugs.debian.org: > severity 830675 normal Bug #830675 [src:golang-github-mesos-mesos-go] golang-github-mesos-mesos-go: accesses the internet during build Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need

Bug#830209: [pkg-go] Bugs: "accesses the internet during build" -- strongly disagree on severity

On Sunday, 10 July 2016 11:28:07 AM AEST Chris Lamb wrote: > Severity: serious > Justification: Policy 4.9 > User: la...@debian.org > Usertags: network-access Hi Chris, Thank you for submitting those bugs. I agree that it is a legitimate problem that needs addressing. However I strongly

Bug#817562: marked as done (libxcrypt: Removal of debhelper compat 4)

Your message dated Mon, 11 Jul 2016 00:05:54 + with message-id and subject line Bug#817562: fixed in libxcrypt 1:2.4-4 has caused the Debian Bug report #817562, regarding libxcrypt: Removal of debhelper compat 4 to be marked as done. This means that you

Bug#830493: Confusion with minetest-mod-mobf

On 09.07.2016 12:08, Julien Puydt wrote: > Hi, > > according to bug #827669 the current minetest-mod-mobf packaging is > buggy/incomplete with a debian/ directory shipped within and probably > missing directories ; in #830493 I pointed out that one of the missing > directories was really a

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

Craig Small writes: > Can you apply this patch to your setup and see if it checks? You really > only need to compile lib/test_strod_nol and run it. With that patch, it succeeds on 123 but then proceeds to fail on 12.34 in my i386 chroot. However, it succeeds fully if I add

Bug#830743: mypy: FTBFS: error: invalid Python installation: unable to open /usr/lib/python3.5/config-3.5m-x86_64-linux-gnu/Makefile

Source: mypy Version: 0.4.2-1 Severity: serious Justification: fails to build from source Hi, mypy FTBFS on the arch:all buildd: https://buildd.debian.org/status/fetch.php?pkg=mypy=all=0.4.2-1=1465515666 fakeroot debian/rules binary-indep dh binary-indep --with python3 --buildsystem=pybuild

Bug#830389: marked as done (pyodbc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found)

Your message dated Sun, 10 Jul 2016 23:00:14 + with message-id and subject line Bug#830389: fixed in pyodbc 3.0.10-2 has caused the Debian Bug report #830389, regarding pyodbc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found to be marked as done. This

Bug#811673: marked as done (FTBFS with GCC 6: cannot convert x to y)

Your message dated Sun, 10 Jul 2016 23:00:13 + with message-id and subject line Bug#811673: fixed in pyodbc 3.0.10-2 has caused the Debian Bug report #811673, regarding FTBFS with GCC 6: cannot convert x to y to be marked as done. This means that you

Processed: reassign 824089 to src:golang-clockwork, fixed 824089 in 0.0~git20141217-1+rm ...

Processing commands for cont...@bugs.debian.org: > # unconfuse the bts > reassign 824089 src:golang-clockwork 0.0~git20141217-1 Bug #824089 {Done: Debian FTP Masters } [golang-clockwork-dev,golang-github-jonboulle-clockwork-dev]

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

Craig Small writes: > Yeah, amd64 doesn't have this problem, I'll probably have to make it > "almost equal" but that's pretty bad way to run tests. For floating point, that can be a necessary evil. :-/ > Ah so you're running i386 kfreebsd (you didn't report it in the other

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

Can you apply this patch to your setup and see if it checks? You really only need to compile lib/test_strod_nol and run it. - Craig On Mon, Jul 11, 2016 at 8:00 AM Craig Small wrote: > On Mon, Jul 11, 2016 at 7:33 AM Aaron M. Ucko wrote: > >> Source:

Bug#807658: marked as done (python-enum: This package will be removed)

Your message dated Sun, 10 Jul 2016 22:37:48 + with message-id and subject line Bug#830710: Removed package(s) from unstable has caused the Debian Bug report #807658, regarding python-enum: This package will be removed to be marked as done. This means

Bug#817536: marked as done (liblingua-de-ascii-perl: Removal of debhelper compat 4)

Your message dated Sun, 10 Jul 2016 22:36:30 + with message-id and subject line Bug#830623: Removed package(s) from unstable has caused the Debian Bug report #817536, regarding liblingua-de-ascii-perl: Removal of debhelper compat 4 to be marked as done.

Bug#830357: marked as done (python-mne: FTBFS: build-dependency not installable: python-vtk)

Your message dated Sun, 10 Jul 2016 22:34:48 + with message-id and subject line Bug#830357: fixed in python-mne 0.12+dfsg-2 has caused the Debian Bug report #830357, regarding python-mne: FTBFS: build-dependency not installable: python-vtk to be marked as

Bug#625835: marked as done (kplayer crashes at startup)

Your message dated Sun, 10 Jul 2016 22:33:17 + with message-id and subject line Bug#830117: Removed package(s) from unstable has caused the Debian Bug report #625835, regarding kplayer crashes at startup to be marked as done. This means that you claim

Processed: tagging 649419, tagging 797941, tagging 795444, tagging 759980, severity of 759980 is serious ...

Processing commands for cont...@bugs.debian.org: > # cleanup tags where versions are sufficient > tags 649419 + sid stretch Bug #649419 [src:gnustep-base] gnustep-base: FTBFS intermittently [amd64]: Hangs in base/NSOperation Added tag(s) sid and stretch. > tags 797941 + stretch Bug #797941

Bug#821978: marked as done (dossizola: Build arch:all+arch:any but is missing build-{arch,indep} targets)

Your message dated Sun, 10 Jul 2016 22:06:47 + with message-id and subject line Bug#821978: fixed in dossizola 1.0-9 has caused the Debian Bug report #821978, regarding dossizola: Build arch:all+arch:any but is missing build-{arch,indep} targets to be

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

On Mon, Jul 11, 2016 at 7:33 AM Aaron M. Ucko wrote: > Source: procps > Version: 2:3.3.12-1 > Severity: serious > Justification: fails to build from source (but built successfully in the > past) > > The i386 build of procps failed with a test suite error (presumably > stemming

Bug#818207: marked as done (opencv: Jasper removal)

Your message dated Sun, 10 Jul 2016 21:51:37 + with message-id and subject line Bug#818207: fixed in opencv 3.0.0+dfsg-1~exp3 has caused the Debian Bug report #818207, regarding opencv: Jasper removal to be marked as done. This means that you claim that

Bug#817585: marked as done (mmake: Removal of debhelper compat 4)

Your message dated Sun, 10 Jul 2016 21:51:17 + with message-id and subject line Bug#817585: fixed in mmake 2.3-7 has caused the Debian Bug report #817585, regarding mmake: Removal of debhelper compat 4 to be marked as done. This means that you claim that

Bug#828712: marked as done (alljoyn-services-1509 and alljoyn-services-1504: error when trying to install together)

Your message dated Sun, 10 Jul 2016 21:49:56 + with message-id and subject line Bug#828712: fixed in alljoyn-services-1509 15.09-2 has caused the Debian Bug report #828712, regarding alljoyn-services-1509 and alljoyn-services-1504: error when trying to

Bug#811643: marked as done (FTBFS with GCC 6: cannot convert x to y)

Your message dated Sun, 10 Jul 2016 21:50:02 + with message-id and subject line Bug#811643: fixed in bloboats 1.0.2+dfsg-2 has caused the Debian Bug report #811643, regarding FTBFS with GCC 6: cannot convert x to y to be marked as done. This means that

Processed: bug is in 15.09-1

Processing commands for cont...@bugs.debian.org: > notfound 828712 15.04-4 Bug #828712 [alljoyn-services-1504,alljoyn-services-1509] alljoyn-services-1509 and alljoyn-services-1504: error when trying to install together There is no source info for the package 'alljoyn-services-1509' at version

Bug#634409: marked as done (libparserutils: FTBFS: src/input/inputstream.c:484:18: error: variable 'utf32' set but not used [-Werror=unused-but-set-variable])

Your message dated Sun, 10 Jul 2016 16:32:19 +0200 with message-id and subject line libparserutils has been removed from Debian in 2012 has caused the Debian Bug report #634409, regarding libparserutils: FTBFS: src/input/inputstream.c:484:18:

Bug#830733: procps: FTBFS[i386]: FAIL: strtod_nol_or_err("123") != 123.000000

Source: procps Version: 2:3.3.12-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The i386 build of procps failed with a test suite error (presumably stemming from a small floating-point discrepancy): FAIL: lib/test_strtod_nol

Bug#830683: Missing dependency on module-udev?

reopen 830683 thanks I know that this split was done by purpose. However even if the split was done on purpose, this split shouldn't break existing systems - which actually happened. It would be nice if you wouldn't close the bug without actually thinking about a solution for this problem, as

Bug#830683: marked as done (no sound anymore after upgrade to 9.0-1.1)

Your message dated Sun, 10 Jul 2016 18:09:25 -0300 with message-id

Processed: fixed 828076 in 1.3.0-1

Processing commands for cont...@bugs.debian.org: > fixed 828076 1.3.0-1 Bug #828076 [src:ruby-saml] ruby-saml: CVE-2016-5697 Marked as fixed in versions ruby-saml/1.3.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 828076:

Bug#830728: golang-github-mattn-go-shellwords: FTBFS: shellwords_test.go:57: fork/exec : no such file or directory

Source: golang-github-mattn-go-shellwords Version: 1.0.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, golang-github-mattn-go-shellwords

Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

Source: golang-github-mitchellh-go-homedir Version: 0.0~git20150831.0.df55a15-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer,

Bug#830727: golang-github-magiconair-properties: FTBFS: go test -v github.com/magiconair/properties [..] circular reference

Source: golang-github-magiconair-properties Version: 1.7.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer,

Bug#623417: marked as done (python-profiler: fails to configure if python2.5 is installed)

Your message dated Sun, 10 Jul 2016 15:28:31 +0200 with message-id <6c8e9489-6981-44ae-97aa-b182f3a17...@debian.org> and subject line closing bugs reported against ancient python versions has caused the Debian Bug report #623417, regarding python-profiler: fails to configure if python2.5 is

Processed: Re: Bug#830718: nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version

Processing control commands: > severity -1 normal Bug #830718 [nvidia-kernel-dkms] nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version Severity set to 'normal' from 'serious' > tags -1 moreinfo Bug #830718 [nvidia-kernel-dkms] nvidia-kernel-dkms: dkms builds

Bug#821347: libsecret porting for s390x

Hello Bastian Blank. On Sun, Jul 10, 2016 at 12:33:12PM +0200, Bastian Blank wrote: > On Sun, Jun 26, 2016 at 10:12:31PM +0200, Andreas Henriksson wrote: > > I'd like to ask for your help with looking at the problems building > > libsecret on s390x. It's currently the only (release-)architecture

Bug#830718: nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version

Control: severity -1 normal Control: tags -1 moreinfo On Sun, 2016-07-10 at 20:19 +0200, Peter Keel wrote: > Package: nvidia-kernel-dkms > Version: 367.27-1 > Severity: serious > Justification: 6 > > Dear Maintainer, > > Installing a new kernel 4.6.3 (self-compiled), and installing the >

Bug#564982: marked as done (facturalux: ftbfs with gcc-4.5)

Your message dated Sun, 10 Jul 2016 16:29:10 +0200 with message-id <7a356c19-e18d-c8b7-b727-6a2c032c6...@debian.org> and subject line facturalux has been removed from Debian in 2011 has caused the Debian Bug report #564982, regarding facturalux: ftbfs with gcc-4.5 to be marked as done. This means

Processed: severity of 817092 is serious

Processing commands for cont...@bugs.debian.org: > severity 817092 serious Bug #817092 [libjs-handlebars] libjs-handlebars: Minified source is non-free Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 817092:

Bug#655370: marked as done (arrayprobe: FTBFS: ls: cannot access /usr/src/linux-source-2.6*.tar.bz2: No such file or directory)

Your message dated Sun, 10 Jul 2016 15:40:55 +0200 with message-id <76f5edb0-026e-9502-8dfd-faf03190c...@debian.org> and subject line arrayprobe has been removed from Debian in 2012 has caused the Debian Bug report #655370, regarding arrayprobe: FTBFS: ls: cannot access

Bug#830718: nvidia-kernel-dkms: dkms builds nvidia kernel modules without module_layout version

Package: nvidia-kernel-dkms Version: 367.27-1 Severity: serious Justification: 6 Dear Maintainer, Installing a new kernel 4.6.3 (self-compiled), and installing the experimental nvidia-drivers a few days later, led to the drivers compiled without module versions. Commandline used: dkms

Bug#830244: auditd: Crash at startup

Package: auditd Version: 1:2.6.3-1 Followup-For: Bug #830244 Addition: I noticed that today the service suddenly started, but only with the standard rules file. As soon as i add anythign to it or use my own separate rules file, the service wont start anymore. But i found out that when using

Bug#827301: marked as done (qgo: FTBFS: network/cyberoroconnection.cpp:524:77: error: narrowing conversion of '250' from 'int' to 'char' inside { })

Your message dated Sun, 10 Jul 2016 17:08:39 + with message-id and subject line Bug#827301: fixed in qgo 2.1~git-20160623-1 has caused the Debian Bug report #827301, regarding qgo: FTBFS: network/cyberoroconnection.cpp:524:77: error: narrowing conversion

Bug#811786: marked as done (qgo: FTBFS with GCC 6: narrowing conversion)

Your message dated Sun, 10 Jul 2016 17:08:39 + with message-id and subject line Bug#811786: fixed in qgo 2.1~git-20160623-1 has caused the Debian Bug report #811786, regarding qgo: FTBFS with GCC 6: narrowing conversion to be marked as done. This means

Bug#829195: ruby-moneta: FTBFS: /usr/lib/ruby/2.3.0/fileutils.rb:1451:in `unlink': No such file or directory @ unlink_internal

> I cannot reproduce this FTBFS in sid as of today - has a broken > dependency been fixed in the meantime? Not sure, but I cannot reproduce either so closing (in BCC). Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#829195: marked as done (ruby-moneta: FTBFS: /usr/lib/ruby/2.3.0/fileutils.rb:1451:in `unlink': No such file or directory @ unlink_internal)

Your message dated Sun, 10 Jul 2016 19:03:42 +0200 with message-id <1468170222.2849045.662072721.3062f...@webmail.messagingengine.com> and subject line Re: ruby-moneta: FTBFS: /usr/lib/ruby/2.3.0/fileutils.rb:1451:in `unlink': No such file or directory @ unlink_internal has caused the Debian

Bug#795444: python-enum: Conflicting module with package 'enum' provided by 'python-enum34'

Followup-For: Bug #795444 Control: clone -1 -2 Control: reassign -2 python-enum34 Control: found -2 1.1.5-1 Control: retitle -2 python-enum34: add Breaks: python-enum Since python-enum is about to be removed from the archive, python-enum34 needs to take care that python-enum gets removed on

Processed: Re: python-enum: Conflicting module with package 'enum' provided by 'python-enum34'

Processing control commands: > clone -1 -2 Bug #795444 {Done: Federico Ceratto } [python-enum] python-enum: Conflicting module with package 'enum' provided by 'python-enum34' Bug 795444 cloned as bug 830712 > reassign -2 python-enum34 Bug #830712 {Done: Federico Ceratto

Bug#817092: this browserified

Control: severity -1 wishlist This is not a minified file, only browserified. Though ideally we should browserify it in debian, grunt is still not packaged. Since its still a human readable and modifiable format, I don't think DFSG applies here. When node-grunt is available in the archive, we

Processed: this browserified

Processing control commands: > severity -1 wishlist Bug #817092 [libjs-handlebars] libjs-handlebars: Minified source is non-free Severity set to 'wishlist' from 'serious' -- 817092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817092 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#638078: marked as done (file-browser-applet: needs porting to new libpanel-applet interface)

Your message dated Sun, 10 Jul 2016 15:58:13 +0200 with message-id <9e62d2d7-6195-779b-f917-b0d5f8a20...@debian.org> and subject line file-browser-applet was removed from Debian in 2012 has caused the Debian Bug report #638078, regarding file-browser-applet: needs porting to new libpanel-applet

Bug#827589: marked as done (ruby-puppet-syntax: FTBFS: PuppetSyntax::Manifests should return an error from an invalid file)

Your message dated Sun, 10 Jul 2016 16:21:19 + with message-id and subject line Bug#827589: fixed in ruby-puppet-syntax 2.1.0-1 has caused the Debian Bug report #827589, regarding ruby-puppet-syntax: FTBFS: PuppetSyntax::Manifests should return an error

Bug#829148: marked as done (alljoyn-gateway-1504: repeated postinst execution creates wrong symlink)

Your message dated Sun, 10 Jul 2016 16:19:46 + with message-id and subject line Bug#829148: fixed in alljoyn-gateway-1504 15.04~git20160606-2 has caused the Debian Bug report #829148, regarding alljoyn-gateway-1504: repeated postinst execution creates

Bug#830707: mariadb-connector-c: FTBFS on all architectures other than amd64 and i386

Source: mariadb-connector-c Version: 2.3.0-1 Severity: serious Tags: patch [ 38%] Building C object libmariadb/CMakeFiles/mariadb_obj.dir/my_context.c.o cd /«PKGBUILDDIR»/obj-aarch64-linux-gnu/libmariadb && /usr/bin/cc -DHAVE_OPENSSL -I/«PKGBUILDDIR»/obj-aarch64-linux-gnu/include

Processed: tagging 830700

Processing commands for cont...@bugs.debian.org: > tags 830700 + upstream Bug #830700 [tiff] CVE-2016-5314: tiff: PixarLogDecode() heap-based buffer overflow Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 830700:

Bug#830111: it is not just gemspec change

Control: forwarded -1 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4691 Since its a major release, gitlab should be changed as well. Fortunately, upstream is already working on it. signature.asc Description: OpenPGP digital signature

Bug#564996: marked as done (gpar2: ftbfs with gcc-4.5)

Your message dated Sun, 10 Jul 2016 13:37:05 +0200 with message-id and subject line gpar2 was removed from Debian in 2011 has caused the Debian Bug report #564996, regarding gpar2: ftbfs with gcc-4.5 to be marked as done. This means that you claim

Bug#830700: CVE-2016-5314: tiff: PixarLogDecode() heap-based buffer overflow

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: tiff Version: 4.0.6-1 Severity: critical Tags: security, fixed-upstream Hi LibTIFF maintainer(s), Kaixiang Zhang from Qihoo 36 and Mathias Svensson from Google discovered heap-based buffer overflow vulnerability from PixarLogDecode()

Processed: Re: Bug#830539: not a bug?

Processing control commands: > reassign -1 fgrun Bug #830539 [src:simgear] simgear: missing libraries breaking reverse-dependencies Bug #830421 [src:simgear] fgrun: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/5/../../../x86_64-linux-gnu/libSimGearScene.a(shExtensions.c.o): undefined reference to

Bug#830539: not a bug?

Control: reassign -1 fgrun Control: retitle -1 fgrun: adjust to static simgear build Control: found -1 fgrun/3.4.0.final-2 On 07/09/2016 11:13 AM, Gianfranco Costamagna wrote: > Hi, I just discovered #638283, do you have any news on this issue? > In case I can fix fgrun instead, I already have

Bug#823379: Elmer version

Hi, Admar, I'm sorry about the delay in your getting a response. Please see inline below. على الجمعـة 24 حزيران 2016 ‫13:25، كتب Admar Schoonen: > Dear Debian maintainers, > > The current version of Elmer in unstable is very old > (6.1.0.svn.5396.dfsg2-4+b2; judging from

Bug#651452: marked as done (illuminator: FTBFS on archs where petsc uses liblam (tsview-tsview.o: undefined reference to symbol 'lam_mpi_byte'))

Your message dated Sun, 10 Jul 2016 15:45:35 +0200 with message-id <75a44dcd-d454-e1c6-f0d9-654fd8629...@debian.org> and subject line illuminator ws removed from Debian in 2013 has caused the Debian Bug report #651452, regarding illuminator: FTBFS on archs where petsc uses liblam (tsview-tsview.o:

Bug#669478: marked as done (illuminator: FTBFS: build-dependency not installable: libpetsc3.1-dev)

Your message dated Sun, 10 Jul 2016 15:45:35 +0200 with message-id <75a44dcd-d454-e1c6-f0d9-654fd8629...@debian.org> and subject line illuminator ws removed from Debian in 2013 has caused the Debian Bug report #669478, regarding illuminator: FTBFS: build-dependency not installable: libpetsc3.1-dev

Bug#830606: python-qtawesome: accesses the internet during build

You are correct, here is the following line in conf.py: intersphinx_mapping = {'https://docs.python.org/': None} Thanks for spotting this. Cheers, Ghis

Processed: fixed 829267 in 2.7.3+dfsg-1

Processing commands for cont...@bugs.debian.org: > fixed 829267 2.7.3+dfsg-1 Bug #829267 [xul-ext-adblock-plus] xul-ext-adblock-plus: no ui in jessie firefox-esr Marked as fixed in versions adblock-plus/2.7.3+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#649419: [Debian GNUstep maintainers] Bug#649419: gnustep-base: FTBFS intermittently [amd64]: Hangs in base/NSOperation

Le 10/07/2016 à 15:13, Emilio Pozuelo Monfort a écrit : > On 10/07/16 12:53, Eric Heintzmann wrote: >> If you have access to these machines, is it possible to see the >> Tests/tests.log file ? >> (Or at next build attempt) > Sorry, I don't (and besides, the trees are removed when the build

Bug#649419: [Debian GNUstep maintainers] Bug#649419: gnustep-base: FTBFS intermittently [amd64]: Hangs in base/NSOperation

On 10/07/16 12:53, Eric Heintzmann wrote: > If you have access to these machines, is it possible to see the > Tests/tests.log file ? > (Or at next build attempt) Sorry, I don't (and besides, the trees are removed when the build ends). You could try to build it on one of the porterboxes though.

Processed: tagging 828814

Processing commands for cont...@bugs.debian.org: > tags 828814 + help Bug #828814 [src:grafana] grafana: FTBFS: sqlstore/sqlstore.go:96: cannot assign to x.Logger Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 828814:

Bug#829353: marked as done (chron: FTBFS: dh_clean: Please specify the compatibility level in debian/compat)

Your message dated Sun, 10 Jul 2016 12:34:11 + with message-id and subject line Bug#829353: fixed in r-cran-rcmdrmisc 1.0-4-2 has caused the Debian Bug report #829353, regarding chron: FTBFS: dh_clean: Please specify the compatibility level in

Processed: reassign 828748 to src:libphonenumber, reassign 829530 to src:linux ..., reassign 683981 to src:krb5 ...

Processing commands for cont...@bugs.debian.org: > # reassigning orphaned bugs to their source package > reassign 828748 src:libphonenumber 7.1.0-3 Bug #828748 [src:libphonennumber] libphonenumber: please make the build reproducible Warning: Unknown package 'src:libphonennumber' Bug reassigned

Processed: Bug#811673 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 811673 pending Bug #811673 [pyodbc] FTBFS with GCC 6: cannot convert x to y Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 811673:

Bug#830389: marked as pending

tag 830389 pending thanks Hello, Bug #830389 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=python-modules/packages/pyodbc.git;a=commitdiff;h=7ca6af7 --- commit

Processed: Bug#830389 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 830389 pending Bug #830389 [src:pyodbc] pyodbc: FTBFS: /bin/sh: 3: pythonpython2.7-dbg: not found Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 830389:

  1   2   >