Processed: Lowering the bug`s severity

Processing commands for cont...@bugs.debian.org: > severity 848859 minor Bug #848859 [src:getfem++] getfem++: FTBFS randomly (failing tests) Severity set to 'minor' from 'serious' > tags 848859 +unreproducible Bug #848859 [src:getfem++] getfem++: FTBFS randomly (failing tests) Added tag(s) unrepro

Bug#848859: Lowering the bug`s severity

severity 848859 minor tags 848859 +unreproducible thanks Hi Santiago, thanks for your bugreport! I tried to reproduce the failing test, building getfem on barriere.d,o 5 times but in all cases it did not failed. Also the last upload of getfem was successfully built on all supported platforms. N

Bug#825256: marked as done (php-horde-editor: depends on unavailable ckeditor3)

Your message dated Tue, 27 Dec 2016 07:03:25 + with message-id and subject line Bug#825256: fixed in php-horde-editor 2.0.4+debian0-8 has caused the Debian Bug report #825256, regarding php-horde-editor: depends on unavailable ckeditor3 to be marked as done. This means that you claim that the

Processed: found 849435 in 10.1.20-2

Processing commands for cont...@bugs.debian.org: > found 849435 10.1.20-2 Bug #849435 [src:mariadb-10.1] mariadb-10.1: CVE-2016-6664 Marked as found in versions mariadb-10.1/10.1.20-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 849435: http://bugs.debian.org/

Bug#842895: mariadb-10.0: CVE-2016-6664 CVE-2016-5617

Control: retitle 842895 mariadb-10.0: CVE-2016-6664 Control: clone 842895 -1 Control: reassign -1 src:mariadb-10.1 Control: retitle -1 mariadb-10.1: CVE-2016-6664 Hi Otto, On Wed, Nov 02, 2016 at 07:27:40AM +0100, Salvatore Bonaccorso wrote: > Source: mariadb-10.0 > Version: 10.0.16-1 > Severity:

Processed: Re: Bug#842895: mariadb-10.0: CVE-2016-6664 CVE-2016-5617

Processing control commands: > retitle 842895 mariadb-10.0: CVE-2016-6664 Bug #842895 [src:mariadb-10.0] mariadb-10.0: CVE-2016-6664 CVE-2016-5617 Changed Bug title to 'mariadb-10.0: CVE-2016-6664' from 'mariadb-10.0: CVE-2016-6664 CVE-2016-5617'. > clone 842895 -1 Bug #842895 [src:mariadb-10.0]

Bug#849371: [Reportbug-maint] Bug#849371: reportbug: Version 7.1.1 crashes at launch

control: severity -1 important control: forcemerge 848692 -1 On Mon, Dec 26, 2016 at 5:23 AM, Jean-Luc Coulon (f5ibh) wrote: > File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 316, in > get_user_id >addr = email.utils.formataddr((realname, email)) > AttributeError: 'str' objec

Processed: Re: [Reportbug-maint] Bug#849371: reportbug: Version 7.1.1 crashes at launch

Processing control commands: > severity -1 important Bug #849371 [reportbug] reportbug: Version 7.1.1 crashes at launch Severity set to 'important' from 'grave' > forcemerge 848692 -1 Bug #848692 [reportbug] reportbug fails with punctuation in name Bug #849371 [reportbug] reportbug: Version 7.1.1

Bug#849428: quickfix: FTBFS: GarbledMessage tests sometimes (randomly?) fail

Source: quickfix Version: 1.14.4+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of quickfix for many architectures failed due to bad outcomes of GarbledMessage tests (one per affected architecture, but with varying details, as summari

Bug#833037: python-factory-boy: missing depends on ipaddress

Chris Lamb writes: > severity 833037 serious > thanks > > Surely this bug is RC severity? :) > >> I'm surprised to see no resolution within 2 months of time for such an >> easy bug to fix. >> >> Brian, if you don't want to take care of this package, I will ask for >> its removal from Debian again

Bug#781155: openbsd-inetd: openbsd-inetd.service should be the main service file

On Apr 10, Michael Biebl wrote: > Ideally, the .service file name and sysv init script do match. > If that is not the case, because upstream chose a different name, my > recommendation is to create a symlink and ship that statically in the > package, i.e. not create it via Alias=. Such a link alr

Bug#848156: marked as done (libtext-unaccent-perl: Segmentation fault on unac_string)

Your message dated Tue, 27 Dec 2016 01:34:08 + with message-id and subject line Bug#848156: fixed in libtext-unaccent-perl 1.08-1.3 has caused the Debian Bug report #848156, regarding libtext-unaccent-perl: Segmentation fault on unac_string to be marked as done. This means that you claim that

Processed: limit source to debhelper, tagging 843163

Processing commands for cont...@bugs.debian.org: > limit source debhelper Limiting to bugs with field 'source' containing at least one of 'debhelper' Limit currently set to 'source':'debhelper' > tags 843163 + pending Bug #843163 [debhelper] dpkg: -V fails on files with \ in the name Added tag(s)

Bug#804549: marked as done (simpleburn: segmentation fault)

Your message dated Mon, 26 Dec 2016 22:04:00 + with message-id and subject line Bug#804549: fixed in simpleburn 1.8.0-1 has caused the Debian Bug report #804549, regarding simpleburn: segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#846686: marked as done (seabios: FTBFS: Error! ROM doesn't fit (131104 > 131072))

Your message dated Mon, 26 Dec 2016 21:19:04 + with message-id and subject line Bug#846686: fixed in seabios 1.10.1-1 has caused the Debian Bug report #846686, regarding seabios: FTBFS: Error! ROM doesn't fit (131104 > 131072) to be marked as done. This means that you claim that the problem

Processed: tagging 840853

Processing commands for cont...@bugs.debian.org: > tags 840853 + pending Bug #840853 [qemu] qemu 2.7 requires linuxboot_dma.bin but does not provide or depend on it Bug #841953 [qemu] libvirt0: virt-install generates "No bootable device" error when using --location option Bug #841974 [qemu] libg

Bug#848919: marked as done (sslsplit FTBFS on mips: cachedsess.t.c:86:F:cache_dsess:cache_dsess_01:0: cache returned no session)

Your message dated Mon, 26 Dec 2016 21:05:15 + with message-id and subject line Bug#848919: fixed in sslsplit 0.5.0+dfsg-2 has caused the Debian Bug report #848919, regarding sslsplit FTBFS on mips: cachedsess.t.c:86:F:cache_dsess:cache_dsess_01:0: cache returned no session to be marked as do

Processed: Re: empire-hub: maintainer address bounces

Processing control commands: > Severity -1 important Bug #809625 [src:empire-hub] empire-hub: maintainer address bounces Severity set to 'important' from 'serious' -- 809625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809625 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

I should add, I also had failures with diffoscope version 64 and older, but no failures on newer versions. It seems likely that one of the changes fixed this bug as a side effect, but I cannot yet tell which one.

Bug#809625: empire-hub: maintainer address bounces

Control: Severity -1 important Hi Angsgar, I'm in contact with the maintainer and the plans to fix this. The "working" email is in CC. Also, I thought about the severity of this bug. I guess for now it is to say this is not serious. One time a fellow DD told me to always ask this question if you

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

Hi. I have built version 66 one hundred times in unstable. The builds were made on 19 different autobuilders. The number of failed builds has been zero. (Previously it failed 10% of the time). If you do not remember what kind of change may have fixed this, then there must be some broken build-dep

Bug#812032: mldemos: FTBFS with GCC 6: needed for in-class initialization

This patch allows the package to build with GCC 6.Index: mldemos-0.5.1/Core/glwidget.h === --- mldemos-0.5.1.orig/Core/glwidget.h +++ mldemos-0.5.1/Core/glwidget.h @@ -114,9 +114,9 @@ public: static const GLint texWidth = 128;

Processed: tag 812032

Processing commands for cont...@bugs.debian.org: > tags 812032 patch Bug #812032 [mldemos] mldemos: FTBFS with GCC 6: needed for in-class initialization Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 812032: http://bugs.debian.org/cg

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

On Mon, Dec 26, 2016 at 07:37:55PM +, Chris Lamb wrote: > Santiago Vila wrote: > > > If I do "python3 -m pytest" afterwards this is what it's shown: > […] > > Note: This is still diffoscope_63 in stretch, not sure if I should > > better try the version in unstable and forget completely about t

Bug#846768: marked as done (ldns: FTBFS: configure: error: OpenSSL found in /usr, but version 0.9.7 or higher is required)

Your message dated Mon, 26 Dec 2016 20:50:08 +0100 with message-id <1482781808.2245653.829954345.7ee2d...@webmail.messagingengine.com> and subject line Re: [Pkg-dns-devel] Bug#846768: ldns: FTBFS: configure: error: OpenSSL found in /usr, but version 0.9.7 or higher is required has caused the Debi

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

On lunes, 26 de diciembre de 2016 20:04:08 ART Andrew Shadura wrote: > On 26/12/16 19:28, Lisandro Damián Nicanor Pérez Meyer wrote: > > Thanks to Eduard Bloch at [bug] I've tried adding > > > > [device] > > wifi.scan-rand-mac-address=no > > > > to /etc/NetworkManager/NetworkManager.conf > > > >

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

Santiago Vila wrote: > If I do "python3 -m pytest" afterwards this is what it's shown: […] > Note: This is still diffoscope_63 in stretch, not sure if I should > better try the version in unstable and forget completely about this > version. Please do so; the icc tests were fixed later and there h

Bug#848403: diffoscope: FTBFS randomly (Fatal Python error: deallocating None)

On Sat, 24 Dec 2016, Ximin Luo wrote: > For all you people that already have single-CPU KVM VMs set up, can you > please try to reduce your test cases that still reproduce the bug? > > For example, can you still reproduce it with `debian/rules clean build`? What > about `python3 -m pytest`? The

Bug#734688: Logs are not rotated for a month

Mathieu Parent wrote... > The actual upstream fix for it is: > https://github.com/logrotate/logrotate/commit/fc1c3eff61edf8e9f0a4bfa980f3a6030a6b271f > > And it is included in version 3.11.0. > > The way forward is to update Debian package to 3.11.0. ACK. This version handles my test cases in a

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

On 26/12/16 19:28, Lisandro Damián Nicanor Pérez Meyer wrote: > Thanks to Eduard Bloch at [bug] I've tried adding > > [device] > wifi.scan-rand-mac-address=no > > to /etc/NetworkManager/NetworkManager.conf > > and updating wpasupplicant... and voilá, WiFi is on again. > > [bug]

Bug#795428: marked as done (OpenSLP 1.2 should not be part of stretch)

Your message dated Mon, 26 Dec 2016 18:54:33 + with message-id and subject line Bug#848025: Removed package(s) from unstable has caused the Debian Bug report #795428, regarding OpenSLP 1.2 should not be part of stretch to be marked as done. This means that you claim that the problem has been

Bug#734688: Logs are not rotated for a month

Control: tag -1 + upstream fixed-upstream Hello, 2016-12-26 1:29 GMT+01:00 Christoph Biedl : > Hello everybody, > > looking at this old but nasty bug that must be fixed for stretch: > > * Trying to understand what goes wrong I wrote a small script that > creates a few scenarios and executes log

Processed: Re: Bug#734688: Logs are not rotated for a month

Processing control commands: > tag -1 + upstream fixed-upstream Bug #734688 [logrotate] Logs are not rotated for a month Added tag(s) fixed-upstream and upstream. -- 734688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734688 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#849077: [pkg-wpa-devel] Bug#849077: wpasupplicant: [Regression] Updating wpasupplicant makes not possible to connect to encrypted WiFi

Thanks to Eduard Bloch at [bug] I've tried adding [device] wifi.scan-rand-mac-address=no to /etc/NetworkManager/NetworkManager.conf and updating wpasupplicant... and voilá, WiFi is on again. [bug] I don't know if it's a bug in the d

Bug#806092: [Pkg-electronics-devel] Bug#806092: proposed fix

Dima Kogan writes: > I'm attaching two patches to fix this. Please review soon if > possible. If I don't hear back by Dec 26, I'll NMU this. That's the > latest possible day to meet the cutoff for stretch. Thank you for your work on this. I see that an upload has happened. Please push this patc

Bug#849362: libstring-diff-perl: FTBFS: test failures with new libyaml-perl

Control: tag -1 patch On Mon, Dec 26, 2016 at 10:59:33AM +0200, Niko Tyni wrote: > Package: libstring-diff-perl > Version: 0.07-1 > Severity: serious > User: debian-p...@lists.debian.org > Usertags: autopkgtest > # Failed test at t/02_diff_fully-pp.t line 16. > # Structures begin differ

Processed: Re: Bug#849362: libstring-diff-perl: FTBFS: test failures with new libyaml-perl

Processing control commands: > tag -1 patch Bug #849362 [libstring-diff-perl] libstring-diff-perl: FTBFS: test failures with new libyaml-perl Added tag(s) patch. -- 849362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849362 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#844965: marked as done (gfal2: FTBFS: dh_install: missing files, aborting)

Your message dated Mon, 26 Dec 2016 17:49:20 + with message-id and subject line Bug#844965: fixed in gfal2 2.12.3-1 has caused the Debian Bug report #844965, regarding gfal2: FTBFS: dh_install: missing files, aborting to be marked as done. This means that you claim that the problem has been d

Bug#828373: marked as done (lcgdm: FTBFS with openssl 1.1.0)

Your message dated Mon, 26 Dec 2016 17:34:51 + with message-id and subject line Bug#828373: fixed in lcgdm 1.9.0-2 has caused the Debian Bug report #828373, regarding lcgdm: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#828264: marked as done (cgsi-gsoap: FTBFS with openssl 1.1.0)

Your message dated Mon, 26 Dec 2016 17:18:33 + with message-id and subject line Bug#828264: fixed in cgsi-gsoap 1.3.10-2 has caused the Debian Bug report #828264, regarding cgsi-gsoap: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#849401: restart silently fails

Package: apcupsd Version: 3.14.12-1.1 Severity: serious apcupsd is correctly configured and running on my machine. I decided to restart it by typing: $ sudo systemctl restart apcupsd and the command didn't report any errors. Looking at the output of the 'ps' command, I couldn't find apcupsd

Bug#847806: marked as done (libopenmpi2: broken SONAME links)

Your message dated Mon, 26 Dec 2016 16:58:44 + with message-id <73ad5d82-0f67-ac62-8541-4707a4e90...@debian.org> and subject line fixed in openmpi_2.0.2~git.20161225-8 has caused the Debian Bug report #847806, regarding libopenmpi2: broken SONAME links to be marked as done. This means that you

Bug#831442: marked as done (mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order)

Your message dated Mon, 26 Dec 2016 16:53:43 + with message-id <284c2442-3274-a191-491e-805c9818b...@debian.org> and subject line fixed in openmpi upload has caused the Debian Bug report #831442, regarding mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order to be mar

Bug#844903: marked as done (lintian: FTBFS: Test failures)

Your message dated Mon, 26 Dec 2016 16:33:30 + with message-id and subject line Bug#844903: fixed in lintian 2.5.50 has caused the Debian Bug report #844903, regarding lintian: FTBFS: Test failures to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#849390: google-android-ndk-installer: Superseded by google-android-installers?

Source: google-android-ndk-installer Version: 13b Severity: serious google-android-ndk-installer was removed from unstable and testing in Sepember because it's been replaced by google-android-installers. See https://bugs.debian.org/838653 google-android-ndk-installer was recently re-introduced bu

Processed: Re: python-factory-boy: missing depends on ipaddress

Processing commands for cont...@bugs.debian.org: > severity 833037 serious Bug #833037 [python-factory-boy] python-factory-boy: missing depends on ipaddress Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 833037: http://

Bug#849388: factory-boy: FTBFS: ImportError: The ``fake-factory`` package is now called ``Faker``.

Source: factory-boy Version: 2.7.0-2 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, factory-boy fails to build from source in unstable/amd64:

Bug#849164: marked as done (virtualbox-ext-pack: dependencies on virtualbox seem to be wrong)

Your message dated Mon, 26 Dec 2016 15:23:53 + with message-id and subject line Bug#849164: fixed in virtualbox-ext-pack 5.1.12-2 has caused the Debian Bug report #849164, regarding virtualbox-ext-pack: dependencies on virtualbox seem to be wrong to be marked as done. This means that you clai

Bug#835686: docker.io: FTBFS: .gopath/src/github.com/docker/containerd/api/grpc/types/api.pb.go:1137: cannot use _API_CreateContainer_Handler (type func(interface {}, "golang.org/x/net/context".Contex

Hello, On Thu, Dec 22, 2016 at 11:10:33AM -0800, Tianon Gravi wrote: > On 22 December 2016 at 11:05, Antonio Terceiro wrote: > > We are very close to a point where docker will not be part of stretch. > > Is there any chance this gets fixed before that? > > If someone were to come up with a patch

Bug#849164: severity is critical

Hello >Gianfranco can give you a real answer, but AFAIK he's off to the family >(such a surprise during Xmas!) thus might not respond immediately -- that's >why I'm telling you about the "pull the plug" workaround. a no change-rebuild fixes this issue, the dependencies are evaluated at build ti

Processed: bug 849362 is forwarded to https://github.com/yappo/p5-String-Diff/issues/6

Processing commands for cont...@bugs.debian.org: > forwarded 849362 https://github.com/yappo/p5-String-Diff/issues/6 Bug #849362 [libstring-diff-perl] libstring-diff-perl: FTBFS: test failures with new libyaml-perl Set Bug forwarded-to-address to 'https://github.com/yappo/p5-String-Diff/issues/6

Bug#848780: marked as done (pyrit: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Mon, 26 Dec 2016 14:24:15 +0100 with message-id and subject line Re: Bug#848780: pyrit: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #848780, regarding pyrit: FTBFS: E: Build killed with signal TERM after 150 minutes o

Bug#849382: [apt] Every package on the system gets silently upgraded to backports. The result is severe system breakage, malfunctioning and data loss.

Package: apt Version: 1.0.9.8.4 Severity: critical --- Please enter the report below this line. --- I use Debian 8 64bit with GNOME installed with standard install procedure from netinstall and using tasksel. This occured to me the second time. First time was a year ago, I reinstalled Debian t

Bug#845861: marked as done (lcgdm: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Mon, 26 Dec 2016 14:17:11 +0100 with message-id <1482758231.5338.2.ca...@physics.uu.se> and subject line Already fixed in previous upload has caused the Debian Bug report #845861, regarding lcgdm: switch to build depend on the metapackage default-libmysqlclient-dev to be marked

Bug#844137: node-groove: FTBFS: Tests failures

Hi, On 26 December 2016 at 05:08, Petter Reinholdtsen wrote: > [Felipe Sateler] >> This suggests there is some wrong thread usage. Andrew, any idea what >> could this be? > > There are several bugs that can trigger this. For example trying to unlock an > non-locked lock. Using 'valgrind --tool=

Bug#818616: What should I do?

Hum, I'm a bit lost here. 2.0.4 is fine, but does not work on arm64. What about 2.1-beta2 + fix allocator (as in message #35) ? Was it tested? Does it work? Should I upload it? Best, -- Enrico Tassi

Bug#848003: marked as done (firejail: Unable to add/remove users/groups when it is running)

Your message dated Mon, 26 Dec 2016 14:00:16 +0100 with message-id <20161226130015.gx19...@reiner-h.de> and subject line Re: Bug#848003: firejail: Unable to add/remove users/groups when it is running has caused the Debian Bug report #848003, regarding firejail: Unable to add/remove users/groups wh

Processed: Re: svgwrite: FTBFS: ImportError: No module named pyparsing

Processing commands for cont...@bugs.debian.org: > tags 829415 patch Bug #829415 [src:svgwrite] svgwrite: FTBFS: ImportError: No module named pyparsing Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 829415: http://bugs.debian.org/cgi-bin/bugr

Bug#829415: svgwrite: FTBFS: ImportError: No module named pyparsing

tags 829415 patch thanks After adding python{,3}-pyparsing as build dependencies, svgwrite built successfully for me locally. See the attached patch. :) -- mvh / best regards Hans Joachim Desserud http://desserud.orgdiff --git a/debian/control b/debian/control index 08b83c3..bf99802 100644 --- a

Bug#776193: unshield: CVE-2015-1386: directory traversal

Upstream just merged the fix, and am preparing a new release. Evgeni, can you pick it up and make a new Debna upload with it today? If we do it quickly enough, it might make it into Stretch. -- Happy hacking Petter Reinholdtsen

Bug#828595: marked as done (voms must (build-)depend on libssl1.0-dev)

Your message dated Mon, 26 Dec 2016 12:35:48 + with message-id and subject line Bug#828595: fixed in voms 2.0.14-2 has caused the Debian Bug report #828595, regarding voms must (build-)depend on libssl1.0-dev to be marked as done. This means that you claim that the problem has been dealt with

Bug#828595: marked as done (voms must (build-)depend on libssl1.0-dev)

Your message dated Mon, 26 Dec 2016 12:35:48 + with message-id and subject line Bug#844877: fixed in voms 2.0.14-2 has caused the Debian Bug report #844877, regarding voms must (build-)depend on libssl1.0-dev to be marked as done. This means that you claim that the problem has been dealt with

Bug#844877: marked as done (voms: FTBFS: sslutils.c:263:33: error: dereferencing pointer to incomplete type 'X509_NAME {aka struct X509_name_st}')

Your message dated Mon, 26 Dec 2016 12:35:48 + with message-id and subject line Bug#844877: fixed in voms 2.0.14-2 has caused the Debian Bug report #844877, regarding voms: FTBFS: sslutils.c:263:33: error: dereferencing pointer to incomplete type 'X509_NAME {aka struct X509_name_st}' to be ma

Bug#844877: marked as done (voms: FTBFS: sslutils.c:263:33: error: dereferencing pointer to incomplete type 'X509_NAME {aka struct X509_name_st}')

Your message dated Mon, 26 Dec 2016 12:35:48 + with message-id and subject line Bug#828595: fixed in voms 2.0.14-2 has caused the Debian Bug report #828595, regarding voms: FTBFS: sslutils.c:263:33: error: dereferencing pointer to incomplete type 'X509_NAME {aka struct X509_name_st}' to be ma

Bug#845901: marked as done (quickfix: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Mon, 26 Dec 2016 12:00:28 + with message-id and subject line Bug#845901: fixed in quickfix 1.14.4+dfsg-1 has caused the Debian Bug report #845901, regarding quickfix: switch to build depend on the metapackage default-libmysqlclient-dev to be marked as done. This means that

Bug#831128: marked as done (quickfix: FTBFS with GCC 6)

Your message dated Mon, 26 Dec 2016 12:00:28 + with message-id and subject line Bug#831128: fixed in quickfix 1.14.4+dfsg-1 has caused the Debian Bug report #831128, regarding quickfix: FTBFS with GCC 6 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#844137: Info received (node-groove: FTBFS: Tests failures)

I got help from Lucas to get access to a machine where the problem is exposed, and have tried to debug a bit further. This was a hard problem to figure out because nodejs hijack the signal pinpointing the exact crash location, and I have not yet understood exactly what go wrong. But I am a bit

Bug#846413: marked as done (at: add libfl-dev to Build-Depends)

Your message dated Mon, 26 Dec 2016 12:10:34 +0100 with message-id <1482750634.2168446.829704113.2ac16...@webmail.messagingengine.com> and subject line Fixed in 3.1.20-2 (UNRELEASED) has caused the Debian Bug report #846413, regarding at: add libfl-dev to Build-Depends to be marked as done. This

Bug#848776: marked as done (at: FTBFS: ./lex.yy.c:1258: undefined reference to `yywrap')

Your message dated Mon, 26 Dec 2016 12:10:34 +0100 with message-id <1482750634.2168446.829704113.2ac16...@webmail.messagingengine.com> and subject line Fixed in 3.1.20-2 (UNRELEASED) has caused the Debian Bug report #846413, regarding at: FTBFS: ./lex.yy.c:1258: undefined reference to `yywrap' to

Bug#848776: marked as done (at: FTBFS: ./lex.yy.c:1258: undefined reference to `yywrap')

Your message dated Mon, 26 Dec 2016 12:10:34 +0100 with message-id <1482750634.2168446.829704113.2ac16...@webmail.messagingengine.com> and subject line Fixed in 3.1.20-2 (UNRELEASED) has caused the Debian Bug report #848776, regarding at: FTBFS: ./lex.yy.c:1258: undefined reference to `yywrap' to

Bug#846413: marked as done (at: add libfl-dev to Build-Depends)

Your message dated Mon, 26 Dec 2016 12:10:34 +0100 with message-id <1482750634.2168446.829704113.2ac16...@webmail.messagingengine.com> and subject line Fixed in 3.1.20-2 (UNRELEASED) has caused the Debian Bug report #848776, regarding at: add libfl-dev to Build-Depends to be marked as done. This

Processed: severity of 848978 is serious

Processing commands for cont...@bugs.debian.org: > severity 848978 serious Bug #848978 [src:courier] Unsuitable to be part of stable release without proper maintainer Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 848978:

Bug#849346: plan to merge packages

This reminds me: we need to revisit the possibility of merging android-platform-external-libunwind with the plain libunwind package. Its such a pain that Android uses all these forks.

Bug#849371: reportbug: Version 7.1.1 crashes at launch

Package: reportbug Version: 6.6.6 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Version 7.1.1 crashes from unstable at start with the following TraceBack: Detected character set: UTF-8 Please change your locale if this is incorrect. T

Bug#848344: marked as done (cgns-convert: /usr/bin/unitconv is already used by xcrysden)

Your message dated Mon, 26 Dec 2016 10:19:12 + with message-id and subject line Bug#848344: fixed in libcgns 3.3.0-3 has caused the Debian Bug report #848344, regarding cgns-convert: /usr/bin/unitconv is already used by xcrysden to be marked as done. This means that you claim that the problem

Bug#849370: aptitude: Aptitude crashes with SIGABRT on install command

Package: aptitude Version: 0.8.3-1+b2 Severity: grave Justification: renders package unusable -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Aptitude crashes with SIGABRT on apt-get install command line or in the "G" command in curses mode. Attached the gdb backtrace. Regards Jean-Luc -

Bug#849368: seaborn: FTBFS: AssertionError: (0.0, 0.0, 1.0, 1.0) != 'blue'

Source: seaborn Version: 0.7.1-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org Dear Maintainer, seaborn fails to build from source in unstable/amd64: […]

Processed: Pending

Processing commands for cont...@bugs.debian.org: > tags 845167 + pending Bug #845167 [src:lemonldap-ng] lemonldap-ng: FTBFS randomly (failing tests) Added tag(s) pending. > End of message, stopping processing here. Please contact me if you need assistance. -- 845167: http://bugs.debian.org/cgi-b

Bug#849365: libphp-phpmailer: CVE-2016-10033

Source: libphp-phpmailer Version: 5.2.9+dfsg-2 Severity: grave Tags: security upstream Justification: user security hole Hi, the following vulnerability was published for libphp-phpmailer. CVE-2016-10033[0]: remote code execution Details though at the point of writing this bugreport are not yet

Bug#848797: marked as done (mpi-defaults: FTBFS: XXX)

Your message dated Mon, 26 Dec 2016 09:33:24 + with message-id and subject line Bug#848797: fixed in mpi-defaults 1.8 has caused the Debian Bug report #848797, regarding mpi-defaults: FTBFS: XXX to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#844235: marked as done (python-ttystatus: FTBFS: ttystatus/fmt.py:31:1: E305 expected 2 blank lines after class or function definition, found 1)

Your message dated Mon, 26 Dec 2016 09:05:09 + with message-id and subject line Bug#844235: fixed in python-ttystatus 0.34-1 has caused the Debian Bug report #844235, regarding python-ttystatus: FTBFS: ttystatus/fmt.py:31:1: E305 expected 2 blank lines after class or function definition, foun

Bug#849362: libstring-diff-perl: FTBFS: test failures with new libyaml-perl

Package: libstring-diff-perl Version: 0.07-1 Severity: serious User: debian-p...@lists.debian.org Usertags: autopkgtest As noticed by ci.debian.net, this package fails its test suite on current sid, making it fail to build from source. This regressed with libyaml-perl_1.21-1. https://ci.debian

Bug#844137: Info received (node-groove: FTBFS: Tests failures)

This is the problem I could find when testing. I have no idea if it is fatal with an TSX CPU. % valgrind --tool=helgrind nodejs /usr/bin/mocha --reporter spec ==18808== Helgrind, a thread error detector ==18808== Copyright (C) 2007-2015, and GNU GPL'd, by OpenWorks LLP et al. ==18808== Using

Bug#844137: node-groove: FTBFS: Tests failures

[Felipe Sateler] > This suggests there is some wrong thread usage. Andrew, any idea what > could this be? There are several bugs that can trigger this. For example trying to unlock an non-locked lock. Using 'valgrind --tool=helgrind' make it possible to see incorrect lock usage. -- Happy hack

Processed: found 849346 in 7.0.0+r1-3

Processing commands for cont...@bugs.debian.org: > found 849346 7.0.0+r1-3 Bug #849346 {Done: Hans-Christoph Steiner } [src:android-platform-external-libunwind] CVE-2015-3239 Marked as found in versions android-platform-external-libunwind/7.0.0+r1-3. > thanks Stopping processing here. Please con