Processed: Re: uwsgi: FTBFS in testing (uwsgiconfig.py: Command not found)

Processing commands for cont...@bugs.debian.org: > block 828785 by 830529 Bug #828785 [src:uwsgi] uwsgi: FTBFS in testing (uwsgiconfig.py: Command not found) 828785 was not blocked by any bugs. 828785 was not blocking any bugs. Added blocking bug(s) of 828785: 830529 > End of message, stopping

Bug#828785: uwsgi: FTBFS in testing (uwsgiconfig.py: Command not found)

Control: block -1 830529 cdbs did some python refactoring recently which broke a feature the uwsgi build depended on. I've reported this to cdbs. https://bugs.debian.org/830529 Thanks, Jeremy Bicha

Bug#811724: marked as done (supertuxkart: FTBFS with GCC 6: narrowing conversion)

Your message dated Sat, 09 Jul 2016 05:20:42 + with message-id and subject line Bug#811724: fixed in supertuxkart 0.9.2-1 has caused the Debian Bug report #811724, regarding supertuxkart: FTBFS with GCC 6: narrowing conversion to be marked as done. This

Bug#830529: cdbs: curpythonindepbinary variable no longer works

Package: cdbs Version: 0.4.142 Severity: serious Justification: causes other package to fail to build from source The uwsgi package has this line [1] in its debian/rules: clean:: $(cdbs_curpythonindepbinary) $(UWSGI_BUILDER) --clean The result is this, as seen in a successful build log [2]:

Bug#811585: Non-Debian patch

For the sake of any non-Debian people who might be interested in this bug, here is the non-Debianised patch, as I forwarded is to the upstream contacts listed in d/copyright. -- Sean Whitton Description: clarify indentation to fix build with GCC 6 Author: Sean Whitton

Processed: tagging 811676

Processing commands for cont...@bugs.debian.org: > tags 811676 + patch Bug #811676 [fbreader] FTBFS with GCC 6: could not convert a from x to y Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 811676:

Bug#828819: marked as done (intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1)

Your message dated Sat, 09 Jul 2016 04:20:06 + with message-id and subject line Bug#828819: fixed in intel-microcode 3.20160607.2 has caused the Debian Bug report #828819, regarding intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1 to

Processed: RFS: clutter-gesture/0.0.2.1-7.1 [NMU, RC] -- Open GL based interactive canvas library Gesture framework

Processing control commands: > block 811585 by -1 Bug #811585 [clutter-gesture] FTBFS with GCC 6: statement indented as if it were guarded by 811585 was not blocked by any bugs. 811585 was not blocking any bugs. Added blocking bug(s) of 811585: 830528 -- 811585:

Processed: clutter-gesture: diff for NMU version 0.0.2.1-7.1

Processing control commands: > tags 811585 + patch Bug #811585 [clutter-gesture] FTBFS with GCC 6: statement indented as if it were guarded by Added tag(s) patch. -- 811585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811585 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#811585: clutter-gesture: diff for NMU version 0.0.2.1-7.1

Control: tags 811585 + patch Dear maintainer, I've prepared an NMU for clutter-gesture (versioned as 0.0.2.1-7.1) and submitted a request for sponsorship to have it uploaded. Regards. -- Sean Whitton diff -Nru clutter-gesture-0.0.2.1/debian/changelog clutter-gesture-0.0.2.1/debian/changelog

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:49:13 + with message-id and subject line Bug#783547: fixed in mgltools-webservices 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:49:07 + with message-id and subject line Bug#767144: fixed in mgltools-volume 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:49:13 + with message-id and subject line Bug#767144: fixed in mgltools-webservices 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:49:07 + with message-id and subject line Bug#783547: fixed in mgltools-volume 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:49:13 + with message-id and subject line Bug#767144: fixed in mgltools-webservices 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:49:07 + with message-id and subject line Bug#767144: fixed in mgltools-volume 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:35:44 + with message-id and subject line Bug#783547: fixed in mgltools-sff 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that you

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:36:10 + with message-id and subject line Bug#783547: fixed in mgltools-utpackages 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:35:51 + with message-id and subject line Bug#783547: fixed in mgltools-support 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:36:34 + with message-id and subject line Bug#783547: fixed in mgltools-visionlibraries 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:35:58 + with message-id and subject line Bug#783547: fixed in mgltools-symserv 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:36:16 + with message-id and subject line Bug#783547: fixed in mgltools-viewerframework 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:36:27 + with message-id and subject line Bug#783547: fixed in mgltools-vision 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:35:16 + with message-id and subject line Bug#783547: fixed in mgltools-pyautodock 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:36:34 + with message-id and subject line Bug#767144: fixed in mgltools-visionlibraries 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:35:37 + with message-id and subject line Bug#783547: fixed in mgltools-scenario2 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:36:34 + with message-id and subject line Bug#767144: fixed in mgltools-visionlibraries 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:34:39 + with message-id and subject line Bug#783547: fixed in mgltools-mglutil 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:35:06 + with message-id and subject line Bug#783547: fixed in mgltools-pmv 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that you

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:34:45 + with message-id and subject line Bug#783547: fixed in mgltools-networkeditor 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:36:10 + with message-id and subject line Bug#767144: fixed in mgltools-utpackages 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:51 + with message-id and subject line Bug#767144: fixed in mgltools-support 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:34:54 + with message-id and subject line Bug#783547: fixed in mgltools-opengltk 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:35:30 + with message-id and subject line Bug#783547: fixed in mgltools-pyglf 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that you

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:44 + with message-id and subject line Bug#767144: fixed in mgltools-sff 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:36:16 + with message-id and subject line Bug#767144: fixed in mgltools-viewerframework 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:58 + with message-id and subject line Bug#767144: fixed in mgltools-symserv 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:36:27 + with message-id and subject line Bug#767144: fixed in mgltools-vision 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:51 + with message-id and subject line Bug#767144: fixed in mgltools-support 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:44 + with message-id and subject line Bug#767144: fixed in mgltools-sff 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:36:10 + with message-id and subject line Bug#767144: fixed in mgltools-utpackages 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:58 + with message-id and subject line Bug#767144: fixed in mgltools-symserv 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:37 + with message-id and subject line Bug#767144: fixed in mgltools-scenario2 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:36:16 + with message-id and subject line Bug#767144: fixed in mgltools-viewerframework 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:37 + with message-id and subject line Bug#767144: fixed in mgltools-scenario2 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:35:23 + with message-id and subject line Bug#783547: fixed in mgltools-pybabel 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:36:27 + with message-id and subject line Bug#767144: fixed in mgltools-vision 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:23 + with message-id and subject line Bug#767144: fixed in mgltools-geomutils 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:39 + with message-id and subject line Bug#767144: fixed in mgltools-mglutil 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:30 + with message-id and subject line Bug#767144: fixed in mgltools-pyglf 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:34:32 + with message-id and subject line Bug#783547: fixed in mgltools-gle 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that you

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:34:23 + with message-id and subject line Bug#783547: fixed in mgltools-geomutils 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:06 + with message-id and subject line Bug#767144: fixed in mgltools-pmv 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:54 + with message-id and subject line Bug#767144: fixed in mgltools-opengltk 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:09 + with message-id and subject line Bug#767144: fixed in mgltools-cadd 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:39 + with message-id and subject line Bug#767144: fixed in mgltools-mglutil 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:23 + with message-id and subject line Bug#767144: fixed in mgltools-pybabel 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:34:16 + with message-id and subject line Bug#783547: fixed in mgltools-dejavu 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:30 + with message-id and subject line Bug#767144: fixed in mgltools-pyglf 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:16 + with message-id and subject line Bug#767144: fixed in mgltools-dejavu 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:33:34 + with message-id and subject line Bug#783547: fixed in autodocktools 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that you

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:33:57 + with message-id and subject line Bug#783547: fixed in mgltools-bhtree 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:23 + with message-id and subject line Bug#767144: fixed in mgltools-geomutils 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#783547: marked as done (TclError: cannot use geometry manager)

Your message dated Sat, 09 Jul 2016 00:34:09 + with message-id and subject line Bug#783547: fixed in mgltools-cadd 1.5.7-1 has caused the Debian Bug report #783547, regarding TclError: cannot use geometry manager to be marked as done. This means that you

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:06 + with message-id and subject line Bug#767144: fixed in mgltools-pmv 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:23 + with message-id and subject line Bug#767144: fixed in mgltools-pybabel 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:16 + with message-id and subject line Bug#767144: fixed in mgltools-pyautodock 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:45 + with message-id and subject line Bug#767144: fixed in mgltools-networkeditor 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:54 + with message-id and subject line Bug#767144: fixed in mgltools-opengltk 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:45 + with message-id and subject line Bug#767144: fixed in mgltools-networkeditor 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:35:16 + with message-id and subject line Bug#767144: fixed in mgltools-pyautodock 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:31 + with message-id and subject line Bug#767144: fixed in mgltools-gle 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:16 + with message-id and subject line Bug#767144: fixed in mgltools-dejavu 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:31 + with message-id and subject line Bug#767144: fixed in mgltools-gle 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:33:34 + with message-id and subject line Bug#767144: fixed in autodocktools 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:33:57 + with message-id and subject line Bug#767144: fixed in mgltools-bhtree 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:33:57 + with message-id and subject line Bug#767144: fixed in mgltools-bhtree 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that

Bug#767145: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:33:34 + with message-id and subject line Bug#767144: fixed in autodocktools 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#767144: marked as done (autodocktools: fails to start the GUI)

Your message dated Sat, 09 Jul 2016 00:34:09 + with message-id and subject line Bug#767144: fixed in mgltools-cadd 1.5.7-1 has caused the Debian Bug report #767144, regarding autodocktools: fails to start the GUI to be marked as done. This means that you

Bug#796608: marked as done (espeakup: Has init script in runlevel S but no matching service file)

Your message dated Sat, 09 Jul 2016 00:18:25 + with message-id and subject line Bug#796608: fixed in espeakup 1:0.71-27.1 has caused the Debian Bug report #796608, regarding espeakup: Has init script in runlevel S but no matching service file to be marked

Processed: owner 811585

Processing commands for cont...@bugs.debian.org: > owner 811585 ! Bug #811585 [clutter-gesture] FTBFS with GCC 6: statement indented as if it were guarded by Owner recorded as Sean Whitton . > thanks Stopping processing here. Please contact me if you need assistance.

Bug#800225: marked as done (recite: Please migrate a supported debhelper compat level)

Your message dated Sat, 09 Jul 2016 00:00:03 + with message-id and subject line Bug#830504: Removed package(s) from unstable has caused the Debian Bug report #800225, regarding recite: Please migrate a supported debhelper compat level to be marked as done.

Bug#830294: marked as done (trn is insecure, and unsuitable for use with untrusted data)

Your message dated Fri, 08 Jul 2016 23:56:30 + with message-id and subject line Bug#830296: Removed package(s) from unstable has caused the Debian Bug report #830294, regarding trn is insecure, and unsuitable for use with untrusted data to be marked as

Bug#825180: marked as done (apq: fails to build from source due to gnat-6 migration)

Your message dated Fri, 08 Jul 2016 23:55:06 + with message-id and subject line Bug#830243: Removed package(s) from unstable has caused the Debian Bug report #825180, regarding apq: fails to build from source due to gnat-6 migration to be marked as done.

Bug#813749: marked as done (mozjs24: Unsatisfiable Build-Depends and Build-Conflicts)

Your message dated Fri, 08 Jul 2016 23:05:44 + with message-id and subject line Bug#813749: fixed in mozjs24 24.2.0-3.1 has caused the Debian Bug report #813749, regarding mozjs24: Unsatisfiable Build-Depends and Build-Conflicts to be marked as done. This

Bug#830510: marked as done (faketime: '/usr/lib/faketime/libfaketime.so.1' from LD_PRELOAD cannot be preloaded)

Your message dated Fri, 08 Jul 2016 22:37:12 + with message-id and subject line Bug#830510: fixed in faketime 0.9.6-6 has caused the Debian Bug report #830510, regarding faketime: '/usr/lib/faketime/libfaketime.so.1' from LD_PRELOAD cannot be preloaded to

Bug#825845: mrpt: FTBFS on big-endian systems, with test suite errors

> ok, rebased with current debian/unstable package and build good > > I did grab the package from unstable, added the commit above, and did a > complete build. > It didn't fail on s390x, so I don't know how to trigger that failure. Well, that's good news, I guess! Thank you for your time. I

Processed: forcibly merging 829557 830517

Processing commands for cont...@bugs.debian.org: > forcemerge 829557 830517 Bug #829557 [lightdm] lightdm 1.18.2-1 breaks D-BUS unless dbus-user-session is installed Bug #829348 [lightdm] lightdm 1.18.2-1 breaks D-BUS unless dbus-user-session is installed Bug #830517 [lightdm] lightdm: Cannot

Bug#812278: marked as done (musl: FTBFS with GCC 6: musl-tools missing files)

Your message dated Fri, 08 Jul 2016 22:05:30 + with message-id and subject line Bug#812278: fixed in musl 1.1.9-1.2 has caused the Debian Bug report #812278, regarding musl: FTBFS with GCC 6: musl-tools missing files to be marked as done. This means that

Bug#830519: [pkg-go] Bug#830519: docker-swarm: FTBFS: docker/swarm/api/flusher.go:8:2: cannot find package "github.com/docker/docker/pkg/ioutils"

On 8 July 2016 at 14:29, Chris Lamb wrote: > src/github.com/docker/swarm/api/flusher.go:8:2: cannot find package > "github.com/docker/docker/pkg/ioutils" in any of: This sounds like another case of #830478, which should've been fixed with src:docker.io 1.11.2~ds1-2 (uploaded

Bug#828819: intel-microcode: i7-6500U doesn't boot in 4/5 cases with 3.20160607.1

Well, more information: Report for the same issue on Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1353103 All reports of this issue being "fixed" by a firmware update (in Debian, Arch and Fedora) are for firmware updates that come with microcode 0x8a already, effectively rendering the

Bug#830521: nvme-cli: Fix regression in nvme-cli 32-bit compatibility

Package: nvme-cli Version: 0.8-1 Severity: serious Tags: patch Justification: FTBFS User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu yakkety ubuntu-patch Hi Breno, After syncing nvme-cli 0.8-1 into Ubuntu yakkety, I noticed that it has failed to build on all of our 32-bit

Bug#830500: redis: FTBFS: Test failure

On Fri, Jul 8, 2016 at 2:36 PM, Chris Lamb wrote: > Interesting. Can't seem to reproduce here in latest sid. Do you have limited > memory or something like that..? Concurrency..? No, the machine has 8 GB of RAM. I also don't recall the machine being heavily loaded when I

Bug#830500: redis: FTBFS: Test failure

tags 830500 + unreproducible thanks Daniel Schepler wrote: > [err]: Test replication partial resync: ok psync (diskless: yes, > reconnect: 1) in tests/integration/replication-psync.tcl > Expected condition '[s -1 sync_partial_ok] > 0' to be true ([s -1 > sync_partial_ok] > 0) Interesting. Can't

Processed: Re: Bug#830500: redis: FTBFS: Test failure

Processing commands for cont...@bugs.debian.org: > tags 830500 + unreproducible Bug #830500 [src:redis] redis: FTBFS: Test failure Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 830500:

Bug#830519: docker-swarm: FTBFS: docker/swarm/api/flusher.go:8:2: cannot find package "github.com/docker/docker/pkg/ioutils"

Source: docker-swarm Version: 1.0.1+dfsg-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, docker-swarm fails to build from source in

Bug#830520: ekg2: FTBFS: install: cannot change permissions of 'debian/ekg2-scripting-perl/usr/share/doc/ekg2-scripting-perl': No such file or directory

Source: ekg2 Version: 1:0.4~pre+20120506.1-12 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, ekg2 fails to build from source in

Processed: Merge 811852 and 823978

Processing commands for cont...@bugs.debian.org: > forcemerge 823978 811852 Bug #823978 [libboost-regex1.58.0] libboost-regex1.58.0: Boost somehow mixes up c_regex_traits and cpp_regex_traits Bug #811852 [libboost-regex1.58.0] freeorion: FTBFS with GCC 6: no match for 811815 was blocked by:

Bug#829557: [Pkg-xfce-devel] Bug#829557: One more confirmation

On Fri, 2016-07-08 at 17:02 +0200, Stephane Bortzmeyer wrote: > Running stretch, I confirm that the problem still exists today (after > a dist-upgrade). > > Installing dbus-user-session AND REBOOTING cured it. Yeah, we're still investigating the problem, but right now I don't have much clues

Processed (with 2 errors): Re: freeorion: FTBFS with GCC 6: no match for

Processing control commands: > reassign 811852 libboost-regex1.58.0 Bug #811852 [libboost-regex1.58.0] freeorion: FTBFS with GCC 6: no match for Ignoring request to reassign bug #811852 to the same package > severity 823978 serious Bug #823978 [libboost-regex1.58.0] libboost-regex1.58.0: Boost

  1   2   3   4   >