Bug#849334: marked as done ([dnscrypt-proxy] dnscrypt-proxy fails to start due to incorrect configuration path on systemd service file)

Your message dated Mon, 26 Dec 2016 06:18:28 + with message-id and subject line Bug#849334: fixed in dnscrypt-proxy 1.8.1-4 has caused the Debian Bug report #849334, regarding [dnscrypt-proxy] dnscrypt-proxy fails to start due to incorrect configuration

Bug#848029: chromium: sound broken after update

Hi all! Sort of good news. I just upgraded after coming back to my desktop and was then having the exact same issue. I tried to track down the offending code, but the diff was enormous, so I couldn't really find anything. I did however, manage to find a temporary solution to the issue, which

Bug#845117: marked as done (ifmail: FTBFS when built with dpkg-buildpackage -A (dpkg-genbuildinfo error))

Your message dated Mon, 26 Dec 2016 04:04:11 + with message-id and subject line Bug#845117: fixed in ifmail 2.14tx8.10-23 has caused the Debian Bug report #845117, regarding ifmail: FTBFS when built with dpkg-buildpackage -A (dpkg-genbuildinfo error) to

Bug#846429: marked as done (ifmail: add libfl-dev to Build-Depends)

Your message dated Mon, 26 Dec 2016 04:04:11 + with message-id and subject line Bug#846429: fixed in ifmail 2.14tx8.10-23 has caused the Debian Bug report #846429, regarding ifmail: add libfl-dev to Build-Depends to be marked as done. This means that you

Bug#812137: FTBFS with GCC 6: statement is indented as if

This patch fixes the issue.Index: mailavenger-0.8.4/libasync/maketables.c === --- mailavenger-0.8.4.orig/libasync/maketables.c +++ mailavenger-0.8.4/libasync/maketables.c @@ -132,7 +132,9 @@ for (i = 0; i < 256; i++)

Bug#849162: marked as done (snapd: Drop unversioned 'Conflicts: snap')

Your message dated Mon, 26 Dec 2016 03:08:57 + with message-id and subject line Bug#849162: fixed in snapd 2.20-2 has caused the Debian Bug report #849162, regarding snapd: Drop unversioned 'Conflicts: snap' to be marked as done. This means that you claim

Processed: tag 812137

Processing commands for cont...@bugs.debian.org: > tags 812137 patch Bug #812137 [mailavenger] FTBFS with GCC 6: statement is indented as if Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need assistance. -- 812137:

Bug#794438: marked as done (Partition manager does not launch)

Your message dated Mon, 26 Dec 2016 03:08:05 + with message-id and subject line Bug#794438: fixed in partitionmanager 3.0.0-1 has caused the Debian Bug report #794438, regarding Partition manager does not launch to be marked as done. This means that you

Processed: tag 830399

Processing commands for cont...@bugs.debian.org: > tags 830399 patch Bug #830399 [src:python-jedi] python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13 Added tag(s) patch. > End of message, stopping processing here. Please contact me if you need

Bug#830399: python-jedi: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13

These two patches fix the errors. Also, python-pytest and python3-pytest must be added as build dependencies.>From de7273e04b3c8e4ca3f8ba32298a5d3d763b3ab3 Mon Sep 17 00:00:00 2001 From: Sid Shanker Date: Sun, 17 May 2015 23:11:02 -0700 Subject: [PATCH] Fixed utf-8

Bug#849345: marked as done (The connman.postrm is plain wrong. It must remove the state dir only on purging)

Your message dated Mon, 26 Dec 2016 01:48:47 + with message-id and subject line Bug#849345: fixed in connman 1.33-3 has caused the Debian Bug report #849345, regarding The connman.postrm is plain wrong. It must remove the state dir only on purging to be

Bug#806092: marked as done (pcb: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

Your message dated Mon, 26 Dec 2016 00:34:16 + with message-id and subject line Bug#806092: fixed in pcb 20140316-3.1 has caused the Debian Bug report #806092, regarding pcb: FTBFS when built with dpkg-buildpackage -A (No such file or directory) to be

Bug#734688: Logs are not rotated for a month

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 logrotate then. Run it in an arbitrary directory like /tmp/ as regular user, with a single parameter in

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

[Petter Reinholdtsen] > A fix for this release critical security issue is now available as a > pull request upstream. I had a look at the upstream patch, and it do not apply cleanly to the code in unstable, as the code has been restructured quite a bit upstream. As unshield is currently missing

Bug#817602: olpc-xo1: Removal of debhelper compat 4

Thanks to Paul Wise for the heads-up. OLPC still has a software and hardware organisation (me), and is using a Debian derivative (Ubuntu) on our latest hardware (NL3), using the Debian packages of Sugar desktop. Debian should drop olpc-xo1, olpc-powerd, and olpc-kbdshim. OLPC models are XO-1,

Bug#849350: marked as done (jimfs: Incomplete debian/copyright?)

Your message dated Mon, 26 Dec 2016 00:05:48 + with message-id and subject line Bug#849350: fixed in jimfs 1.1-2 has caused the Debian Bug report #849350, regarding jimfs: Incomplete debian/copyright? to be marked as done. This means that you claim that

Bug#846799: Pending fixes for bugs in the golang-google-cloud package

Dmitry, On 16/12/16 19:30, Dmitry Smirnov wrote: >> Ensure the transition from symlink to directory is handled correctly. >> Closes: #846799 > > Thanks for fixing this problem. FYI there is a better way to do that. > Instead of duplicated section in preinst/postinst/postrm you can use one

Processed: Pending fixes for bugs in the jimfs package

Processing commands for cont...@bugs.debian.org: > tag 849350 + pending Bug #849350 [src:jimfs] jimfs: Incomplete debian/copyright? Warning: Unknown package 'src:jimfs' Added tag(s) pending. Warning: Unknown package 'src:jimfs' > thanks Stopping processing here. Please contact me if you need

Bug#849350: Pending fixes for bugs in the jimfs package

tag 849350 + pending thanks Some bugs in the jimfs package are closed in revision d3c825ff34ffbd7db24302e5cbf82b735e7d2494 in branch 'master' by Hans-Christoph Steiner The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/jimfs.git/commit/?id=d3c825f Commit message: add

Processed: python3-django-macaddress: Compatibility of django-macaddress with django 1.10 in stretch

Processing control commands: > severity -1 grave Bug #848073 [python3-django-macaddress] python3-django-macaddress: Compatibility of django-macaddress with django 1.10 in stretch Severity set to 'grave' from 'important' -- 848073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848073 Debian

Bug#849346: marked as done (CVE-2015-3239)

Your message dated Sun, 25 Dec 2016 23:33:51 + with message-id and subject line Bug#849346: fixed in android-platform-external-libunwind 7.0.0+r1-4 has caused the Debian Bug report #849346, regarding CVE-2015-3239 to be marked as done. This means that

Bug#849350: jimfs: Incomplete debian/copyright?

Source: jimfs Version: 1.1-1 Severity: serious Justication: Policy 12.5 X-Debbugs-CC: Hans-Christoph Steiner Hi, I just ACCEPTed jimfs from NEW but noticed it was missing attribution in debian/copyright for the embedded murmurhash implementation. (This is not exhaustive so

Bug#806092: proposed fix

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. >From 65bd793529cc6aae5f6f1946396cde03e55a2620 Mon Sep 17 00:00:00 2001 From: Dima Kogan Date:

Processed: fix version for 842347

Processing commands for cont...@bugs.debian.org: > # identical found and fixed versions confuse version tracking > # removing the fixed version > notfixed 842347 3.2-7 Bug #842347 {Done: Santiago Vila } [src:mpich] mpich: FTBFS randomly (cannot find

Bug#817602: olpc-xo1: Removal of debhelper compat 4

Quoting Adam Borowski (2016-12-25 23:23:32) > On Sun, Dec 25, 2016 at 06:06:12PM +0100, Jonas Smedegaard wrote: > > > I'm pretty sure they haven't produced XO-1s in close to a decade, and > > > that us what my packages are for. XO-1.5 and XO-4 were never > > > supported without additional

Bug#829452: marked as done (axel: FTBFS with openssl 1.1.0)

Your message dated Sun, 25 Dec 2016 22:33:30 + with message-id and subject line Bug#829452: fixed in axel 2.12-1 has caused the Debian Bug report #829452, regarding axel: FTBFS with openssl 1.1.0 to be marked as done. This means that you claim that the

Bug#835456: FTBFS: t/refhang.t test fail on s390x

Control: found -1 1.4.28-1 Control: retitle -1 FTBFS: t/refhang.t test fail Hi, On Thu, Aug 25, 2016 at 10:27:33PM +0200, g...@iroqwa.org wrote: > Just for the record, the upstream test suite fail on s390x > > https://buildd.debian.org/status/fetch.php?pkg=memcached=s390x=1.4.31-1=1471823136 >

Processed: Re: FTBFS: t/refhang.t test fail on s390x

Processing control commands: > found -1 1.4.28-1 Bug #835456 [src:memcached] FTBFS: t/refhang.t test fail on s390x Marked as found in versions memcached/1.4.28-1. > retitle -1 FTBFS: t/refhang.t test fail Bug #835456 [src:memcached] FTBFS: t/refhang.t test fail on s390x Changed Bug title to

Bug#831930: marked as done (spkproxy: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

Your message dated Sun, 25 Dec 2016 22:23:07 + with message-id and subject line Bug#831930: fixed in spkproxy 1.4.8-4.4 has caused the Debian Bug report #831930, regarding spkproxy: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build

Bug#836885: Re-add heimdal-multidev?

On Sun, Dec 25, 2016 at 01:03:15PM -0800, Ryan Tandy wrote: > On Sun, Dec 25, 2016 at 09:05:15PM +0100, Michael Fladischer wrote: > > Now that heimdal has some upstream activity again and 7.1.0 has been > > uploaded to unstable, is there a chance that openldap will reenable > > support for "krb5"

Bug#846854: nagios2mantis: Don't depend on nagios3 which has been removed from unstable

On Sat, Dec 03, 2016 at 06:54:26PM +0100, Bas Couwenberg wrote: > Source: nagios2mantis > Version: 3.1-1.1 > Severity: normal > Tags: patch > > Dear Maintainer, > > Please update your package to deal with the nagios3 removal from Debian > (#845765). Or let's simply remove nagios2mantis, after

Processed: severity of 849243 is important, severity of 848655 is important, forcibly merging 848655 849243

Processing commands for cont...@bugs.debian.org: > severity 849243 important Bug #849243 [reportbug] reportbug: TypeError: * wants int Severity set to 'important' from 'grave' > severity 848655 important Bug #848655 [reportbug] reportbug crashes with error "TypeError: * wants int" Severity set to

Bug#849346: CVE-2015-3239

Source: android-platform-external-libunwind Severity: grave Tags: security Hi, https://security-tracker.debian.org/tracker/CVE-2015-3239 has been fixed in src:unwind, but is still needed in android-platform-external-libunwind Cheers, Moritz

Bug#831920: marked as done (newbiedoc: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build with no binary artifacts found; cannot distribute)

Your message dated Sun, 25 Dec 2016 21:33:52 + with message-id and subject line Bug#831920: fixed in newbiedoc 0.8.0-2.1 has caused the Debian Bug report #831920, regarding newbiedoc: FTBFS with dpkg-buildpackage -A: dpkg-genchanges: error: binary build

Bug#849345: The connman.postrm is plain wrong. It must remove the state dir only on purging

Package: connman Version: 1.33-2 Severity: serious Dear Maintainer, that goes in per incident - reverting this would fix the situation. Cheers Alf -- System Information: Debian Release: stretch/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (500,

Bug#842007: marked as done (python-pyftpdlib: FTBFS (test_on_incomplete_file_received fails))

Your message dated Sun, 25 Dec 2016 21:12:07 + with message-id and subject line Bug#842007: fixed in python-pyftpdlib 1.5.1-3 has caused the Debian Bug report #842007, regarding python-pyftpdlib: FTBFS (test_on_incomplete_file_received fails) to be marked

Bug#836885: Re-add heimdal-multidev?

On Sun, Dec 25, 2016 at 09:05:15PM +0100, Michael Fladischer wrote: Now that heimdal has some upstream activity again and 7.1.0 has been uploaded to unstable, is there a chance that openldap will reenable support for "krb5" in "olcSmbK5PwdEnable"? I really hope we can, but right now I'm

Bug#848419: trac-announcer: FTBFS in stretch (failing tests)

It seems, that trac-announcer is not yet compatible with current trac. The package will therefore not be in stretch. If a fixed version is released, we can deliver it via backports.

Bug#842007: marked as pending

tag 842007 pending thanks Hello, Bug #842007 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/python-pyftpdlib.git;a=commitdiff;h=095d22b --- commit

Processed: Bug#842007 marked as pending

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

Bug#817602: olpc-xo1: Removal of debhelper compat 4

Quoting Andres Salomon (2016-12-25 06:26:43) > On December 24, 2016 7:24:00 PM PST, Paul Wise wrote: >>On Sun, Dec 25, 2016 at 10:38 AM, Andres Salomon wrote: >> >>> Thanks for the patch. Given that OLPC isn't really alive any more, >>> I'm thinking the OLPC packages should

Bug#836885: Re-add heimdal-multidev?

Now that heimdal has some upstream activity again and 7.1.0 has been uploaded to unstable, is there a chance that openldap will reenable support for "krb5" in "olcSmbK5PwdEnable"? Cheers, Michael

Bug#817490: marked as done (hashcash: Removal of debhelper compat 4)

Your message dated Sun, 25 Dec 2016 19:33:55 + with message-id and subject line Bug#817490: fixed in hashcash 1.21-2 has caused the Debian Bug report #817490, regarding hashcash: Removal of debhelper compat 4 to be marked as done. This means that you

Processed: severity of 849136 is important

Processing commands for cont...@bugs.debian.org: > severity 849136 important Bug #849136 [src:gdk-pixbuf] gdk-pixbuf FTBFS on mips64el: pixbuf-randomly-modified test failures Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance.

Bug#817376: marked as done (bicyclerepair: Removal of debhelper compat 4)

Your message dated Sun, 25 Dec 2016 19:18:54 + with message-id and subject line Bug#817376: fixed in redet 8.26-1.2 has caused the Debian Bug report #817376, regarding bicyclerepair: Removal of debhelper compat 4 to be marked as done. This means that you

Bug#828287: marked as done (dsniff: FTBFS with openssl 1.1.0)

Your message dated Sun, 25 Dec 2016 16:51:36 -0200 with message-id

Bug#828525: qupzilla: diff for NMU version 1.8.9~dfsg1-3.1

Thank you very much, Andrey! Andrey Rahmatullin a écrit : > > > Dear maintainer, > > I've prepared an NMU for qupzilla (versioned as 1.8.9~dfsg1-3.1). The diff > is attached to this message. > > Regards. > > -- > WBR, wRAR > diff -Nru qupzilla-1.8.9~dfsg1/debian/changelog >

Bug#849334: [dnscrypt-proxy] dnscrypt-proxy fails to start due to incorrect configuration path on systemd service file

Package: dnscrypt-proxy Version: 1.8.1-3 Severity: serious --- Please enter the report below this line. --- Since last upgrade, Dnscrypt fails to start due search configuration file at path that does not exist. Service file (/lib/systemd/system/dnscrypt-proxy.service) has incorrect path on

Processed: Re: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

Processing commands for cont...@bugs.debian.org: > tags 849333 + patch Bug #849333 [src:faker] faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 849333:

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

forwarded 849333 https://github.com/joke2k/faker/pull/441 thanks I've forwarded this upstream here: https://github.com/joke2k/faker/pull/441 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

tags 849333 + patch thanks Patch attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/faker/providers/ssn/fi_FI/__init__.py b/faker/providers/ssn/fi_FI/__init__.py index 44d9ff3..bba2c0b 100644 ---

Processed: Re: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

Processing commands for cont...@bugs.debian.org: > forwarded 849333 https://github.com/joke2k/faker/pull/441 Bug #849333 [src:faker] faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError Set Bug forwarded-to-address to 'https://github.com/joke2k/faker/pull/441'. >

Bug#849333: faker: Non-determistically FTBFS due to tests sometimes exposing UnboundLocalError

Source: faker Version: 0.7.7-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, faker's testsuite appears to non-deterministically vary in

Bug#848266: marked as done (libparanoid-perl: FTBFS: tests timeout)

Your message dated Sun, 25 Dec 2016 17:48:28 + with message-id and subject line Bug#848266: fixed in libparanoid-perl 2.04-2 has caused the Debian Bug report #848266, regarding libparanoid-perl: FTBFS: tests timeout to be marked as done. This means that

Processed: bug 848266 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=119462

Processing commands for cont...@bugs.debian.org: > forwarded 848266 https://rt.cpan.org/Ticket/Display.html?id=119462 Bug #848266 [src:libparanoid-perl] libparanoid-perl: FTBFS: tests timeout Set Bug forwarded-to-address to 'https://rt.cpan.org/Ticket/Display.html?id=119462'. > thanks Stopping

Processed: found 849264 in 53.0.2785.143-1

Processing commands for cont...@bugs.debian.org: > found 849264 53.0.2785.143-1 Bug #849264 [src:chromium-browser] chromium-browser: copyright file is incomplete Marked as found in versions chromium-browser/53.0.2785.143-1. > thanks Stopping processing here. Please contact me if you need

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

Jérémy Bobbio wrote: > > I deliberately used python3 to match the behaviour of what the > > /usr/bin/enjarify script does. > > Guess it's worth adding a comment about it for future readers. :) Excellent point; added in 53c649cef48de11e1584a09795ad890dcdb95eb4. Regards, -- ,''`. :

Bug#849126: marked as done (FTBFS: several errors when building)

Your message dated Sun, 25 Dec 2016 15:18:59 + with message-id and subject line Bug#849126: fixed in logtools 0.13e has caused the Debian Bug report #849126, regarding FTBFS: several errors when building to be marked as done. This means that you claim

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

OK, I will re-upload directly to ftp-master. Andreas, since you already moved and cleaned up skimage: would you do the same for pandas and statsmodels? For statsmodels, I will already put the new VCS into d/control and do a team upload (pushing the changes as soon as the git is there). Cheers

Processed: Re: Bug#849261: webcamd: FTBFS in testing (no binary artifacts)

Processing control commands: > tags 849261 pending Bug #849261 [src:webcamd] webcamd: FTBFS in testing (no binary artifacts) Added tag(s) pending. -- 849261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849261 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#849260: gav-themes: FTBFS in testing (no binary artifacts)

Control: tags 849260 pending Santiago Vila wrote... > Dear maintainer: > > I tried to build this package with "dpkg-buildpackage -A" > (which is what the "Arch: all" autobuilder would do to build it) > but it failed: Only the NMUer is to blame for this. So in a last-minute attempt to fix this

Bug#849261: webcamd: FTBFS in testing (no binary artifacts)

Control: tags 849261 pending Santiago Vila wrote... > Dear maintainer: >· > I tried to build this package with "dpkg-buildpackage -A" > (which is what the "Arch: all" autobuilder would do to build it) > but it failed: Only the NMUer is to blame for this. So in a last-minute attempt to fix this

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

On December 25, 2016 7:29:09 AM EST, Ole Streicher wrote: >Hi Yaroslav, Michael,Andreas, > >I uploaded the NMU as release 1.1 to DELAYED/2 now. I preferred NMU >since I am not a NeuroDebian team member. > >And I would (again) propose to move the package to debian-science. It

Processed: Re: Bug#849260: gav-themes: FTBFS in testing (no binary artifacts)

Processing control commands: > tags 849260 pending Bug #849260 [src:gav-themes] gav-themes: FTBFS in testing (no binary artifacts) Added tag(s) pending. -- 849260: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

Hi Yaroslav, Michael,Andreas, I uploaded the NMU as release 1.1 to DELAYED/2 now. I preferred NMU since I am not a NeuroDebian team member. And I would (again) propose to move the package to debian-science. It would also be useful to have it with the default structure (with upstream and

Bug#849142: [PATCH] Update dex_expected_diffs and test requirement to ensure test compatibility with enjarify >= 1.0.3. (Closes: #849142)

Chris Lamb: > Daniel Shahaf wrote: > > > > +if subprocess.call( > > > +('python3', '-c', 'import enjarify.typeinference'), > > > > Use sys.executable instead of hardcoding 'python3', to handle the case > > that there's more than one python3 binary on the system? > > I deliberately

Bug#845050: marked as done (python-hpilo FTBFS in stretch due to missing python-cloud-sptheme)

Your message dated Sun, 25 Dec 2016 12:51:34 +0100 with message-id <20161225115134.GA13457@sx> and subject line Re: #845050: python-hpilo FTBFS in stretch due to missing python-cloud-sptheme has caused the Debian Bug report #845050, regarding python-hpilo FTBFS in stretch due to missing

Processed: tag 806037

Processing commands for cont...@bugs.debian.org: > tags 806037 + pending Bug #806037 [src:gnumail] gnumail: FTBFS when built with dpkg-buildpackage -A (No such file or directory) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 806037:

Processed: block 845050 with 829230

Processing commands for cont...@bugs.debian.org: > block 845050 with 829230 Bug #845050 [src:python-hpilo] python-hpilo FTBFS in stretch due to missing python-cloud-sptheme 845050 was blocked by: 829230 845050 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #845050 to

Bug#849164: severity is critical

On Sun, Dec 25, 2016 at 11:08:58AM +, Pedro Ribeiro wrote: > severity 849164 critical To issue a command, you need to either CC control@b.d.o or prefix the pseudoheader with "Control: ". > critical as the package cannot be installed Nope, "critical" applies if the bug: * breaks the whole

Bug#849063: marked as done (src:haskell-mode: maintainer address bounces)

Your message dated Sun, 25 Dec 2016 11:33:36 + with message-id and subject line Bug#849063: fixed in haskell-mode 16.1-2 has caused the Debian Bug report #849063, regarding src:haskell-mode: maintainer address bounces to be marked as done. This means that

Bug#849164: severity is critical

severity 849164 critical critical as the package cannot be installed, and after upgrading virtualbox I cannot start previously suspended VM's

Bug#824738: marked as done (simpleparse: FTBFS: ImportError: No module named simpleparse.stt.TextTools)

Your message dated Sun, 25 Dec 2016 10:35:05 + with message-id and subject line Bug#824738: fixed in simpleparse 2.2.0-1 has caused the Debian Bug report #824738, regarding simpleparse: FTBFS: ImportError: No module named simpleparse.stt.TextTools to be

Bug#849082: marked as done (libapache2-mod-perl2: FTBFS: test failures with Apache 2.4.25)

Your message dated Sun, 25 Dec 2016 10:33:46 + with message-id and subject line Bug#849082: fixed in libapache2-mod-perl2 2.0.10-2 has caused the Debian Bug report #849082, regarding libapache2-mod-perl2: FTBFS: test failures with Apache 2.4.25 to be

Bug#849315: ruby-rabl: FTBFS: Rabl::Engine without bson root #attribute asserts that it can add attribute under a different key name

Source: ruby-rabl Version: 0.13.0-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, ruby-rabl fails to build from source in unstable/amd64:

Processed: Bug#824738 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 824738 pending Bug #824738 [src:simpleparse] simpleparse: FTBFS: ImportError: No module named simpleparse.stt.TextTools Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 824738:

Bug#824738: marked as pending

tag 824738 pending thanks Hello, Bug #824738 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/simpleparse.git;a=commitdiff;h=087e956 --- commit

Bug#848782: statsmodels: FTBFS: TypeError: 'float' object cannot be interpreted as an index

I'll upload to DELAYED ASAP (need to learn how to do this anyway); however the unresolved problem is still the pandas FTBFS. Without that, statsmodels will not migrate. Cheers Ole On 25.12.2016 08:34, Andreas Tille wrote: > Hi Ole, > >> the attached patch fixes the FTBFS. What is the schedule

Bug#811986: marked as done (qwtplot3d: FTBFS with GCC 6: symbol changes)

Your message dated Sun, 25 Dec 2016 09:34:51 + with message-id and subject line Bug#811986: fixed in qwtplot3d 0.2.7+svn191-10.1 has caused the Debian Bug report #811986, regarding qwtplot3d: FTBFS with GCC 6: symbol changes to be marked as done. This

Bug#811986: qwtplot3d: diff for NMU version 0.2.7+svn191-10.1

Graham Inggs writes: > Hi Arto > > On 23 December 2016 at 14:59, Arto Jantunen wrote: >> I've prepared an NMU for qwtplot3d (versioned as 0.2.7+svn191-10.1) and >> uploaded it to DELAYED/5. Please feel free to tell me if I >> should delay it longer. > >

Bug#849277: marked as done (A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading)

Your message dated Sun, 25 Dec 2016 09:03:26 + with message-id and subject line Bug#849277: fixed in bbdb3 3.1.2-7 has caused the Debian Bug report #849277, regarding A typo, "flavor", which evaluates to nothing, prevents bbdb3 from loading to be marked

Bug#811986: qwtplot3d: diff for NMU version 0.2.7+svn191-10.1

Hi Arto On 23 December 2016 at 14:59, Arto Jantunen wrote: > I've prepared an NMU for qwtplot3d (versioned as 0.2.7+svn191-10.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should delay it longer. Thanks for the upload. I'm not the maintainer, but I