Processed: tagging 835278

Processing commands for cont...@bugs.debian.org: > tags 835278 + fixed-in-experimental Bug #835278 {Done: Dmitry Bogatov } [runit] [runit] fails to upgrade cleanly Bug #835903 {Done: Dmitry Bogatov } [runit] runit: upgrade failed Added tag(s)

Bug#830377: Reduce bug`s severity?

On 03/09/16 at 22:37 +0200, Anton Gladky wrote: > Hi all, > > it looks like this test failure is the random case. I was not > able to reproduce it building it 2 times on barriere.debian.org. > > I propose to reduce the bug severity to "normal". I gave it another try, and it fails reproducibly

Bug#830568: python-asyncssh: accesses the internet during build

> Santiago Vila wrote: > > > This is not just a privacy issue but also a reproducibility issue. […] > In this case, there is no reproducibility issue. (I agree; this a different issue to the one being discussed in this bug. Obviously, no package build should execute code downloaded from the

Processed: Re: Bug#835536 closed by Dominic Hargreaves <d...@earth.li> (Bug#835536: fixed in request-tracker4 4.2.13-1)

Processing control commands: > tag -1 patch Bug #835536 [src:request-tracker4] request-tracker4: FTBFS with gnupg 2.1 Added tag(s) patch. -- 835536: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#835536: closed by Dominic Hargreaves <d...@earth.li> (Bug#835536: fixed in request-tracker4 4.2.13-1)

Control: tag -1 patch On Sun, Sep 04, 2016 at 11:17:50AM +0300, Niko Tyni wrote: > However, while building with --add-depends=sbuild fixes (most?) of > the gnupg issues, we also have new failures - probably related to perl > removing cwd from @INC in 5.22.2-4 (which happened after the 4.2.13-1 >

Bug#836599: forwarded upstream

control: forwarded -1 https://github.com/Shark-ML/Shark/issues/112 Forwarded upstream. Not sure whether this package was intended to work on these architectures, so upstream might just not care about this. I'll wait for their reply. The options are: - Upstream fixes it hopefully. - Disable

Processed: forwarded upstream

Processing control commands: > forwarded -1 https://github.com/Shark-ML/Shark/issues/112 Bug #836599 [src:shark] shark: FTBFS on mips/mipsel: test errors Set Bug forwarded-to-address to 'https://github.com/Shark-ML/Shark/issues/112'. -- 836599:

Bug#836669: caja: Crashes due to theme errors

Package: caja Version: 1.14.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, Whenever I try to start caja it crashes with the following errors: (caja:14027): Gtk-WARNING **: Theme parsing error: mate-applications.css:415:16: not a number (caja:14027): Gtk-WARNING

Processed: tagging 835117

Processing commands for cont...@bugs.debian.org: > # not in jesie > tags 835117 + sid stretch Bug #835117 [src:linthesia] linthesia: FTBFS: bind.h:2116:10: error: no matching function for call to 'sigc::bind_functor<-1, sigc::bound_mem_functor3 Added tag(s) sid and stretch. > thanks Stopping

Bug#820965: marked as pending

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

Processed: tagging 834180

Processing commands for cont...@bugs.debian.org: > # not in jessie > tags 834180 + sid stretch Bug #834180 [src:bristol] bristol: FTBFS: audioEngineJack.c:42:26: fatal error: alsa/iatomic.h: No such file or directory Added tag(s) sid and stretch. > tags 834246 + sid stretch Bug #834246

Bug#836571: jessie-pu: package rabbitvcs/0.16-1

Control: tags -1 +confirmed -patch +jessie Control: severity -1 normal On Sun, 2016-09-04 at 07:32 +0100, Christopher Hoskin wrote: > Package: release.debian.org > Severity: critical *No*. The bug you're fixing may be critical, the request to fix it in stable is at most normal. > Tags: patch >

Processed: Re: Bug#836571: jessie-pu: package rabbitvcs/0.16-1

Processing control commands: > tags -1 +confirmed -patch +jessie Bug #836571 [release.debian.org] jessie-pu: package rabbitvcs/0.16-1 Added tag(s) confirmed. Bug #836571 [release.debian.org] jessie-pu: package rabbitvcs/0.16-1 Removed tag(s) patch. Bug #836571 [release.debian.org] jessie-pu:

Bug#836670: strip-nondeterminism: leaves temporary files behind

* Jakub Wilk , 2016-09-04, 16:16: https://jenkins.debian.net/job/lintian-tests_sid/lastFailedBuild/consoleText This URL is better: https://jenkins.debian.net/job/lintian-tests_sid/1267/consoleText The relevant part is: tests::changelog-file-general: diff -u

Bug#814183: openmpi 1.10.2 is broken on powerpc

On Fri, 12 Feb 2016 00:17:28 +0100 Emilio Pozuelo Monfort wrote: > On Tue, 9 Feb 2016 21:49:29 +0200 Graham Inggs wrote: > > Petsc rebuilt successfully [1] a couple of hours ago on poulenc.d.o. [2]. > > My previous tests were done on partch.d.o. [3]. Partch

Bug#832447: perl: apply CVE-2016-1238 fixes to 5.24

Version: 5.24.1~rc3-1 On Mon, Jul 25, 2016 at 04:39:16PM +0100, Dominic Hargreaves wrote: > Source: perl > Version: 5.24.0-1 > Severity: critical > > As a reminder, fixes equivalent to those applied to jessie and sid today > should also be applied to experimental. Done in 5.24.1~rc3-1, but I

Bug#832447: marked as done (perl: apply CVE-2016-1238 fixes to 5.24)

Your message dated Sun, 4 Sep 2016 17:42:07 +0300 with message-id <20160904144207.s4shjj66mctupdz6@estella.local.invalid> and subject line Re: Bug#832447: perl: apply CVE-2016-1238 fixes to 5.24 has caused the Debian Bug report #832447, regarding perl: apply CVE-2016-1238 fixes to 5.24 to be

Bug#836611: chromium: crash after upgrade 52.0.2743.116-2 -> 53.0.2785.89-1

I just wanted to confirm this bug. I'm having the exact same issue after upgrading to 53.0.2785.89-1. All extensions crash and every page/tab (including the home page) comes up with the "Aw snap!" error page. No pages load.  On Sun, 4 Sep 2016 15:02:12 +0200 (CEST) Cristian Ionescu-Idbohrn

Processed: tagging 835416

Processing commands for cont...@bugs.debian.org: > # not in jessie > tags 835416 + sid stretch Bug #835416 [src:imagevis3d] imagevis3d: FTBFS: singleton.hpp:131: undefined reference to `boost::serialization::singleton_module::is_locked()' Added tag(s) sid and stretch. > thanks Stopping

Bug#836678: regina-normal: FTBFS: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

Thanks for the report. > /«PKGBUILDDIR»/engine/snappea/kernel/tables.c:229:67: error: narrowing > conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing] I believe this is fixed by declaring the elements of index_by_permutation[] as signed char, not just char. Caveat: I haven’t tried

Bug#836682: python-wordpresslib: No longer works

Package: python-wordpresslib Version: 1.1-2 Severity: grave Tags: upstream Justification: renders package unusable Dear myself, It appears that wordpress has changed API recently, so this is not working. Since upstream seems dead and there is no hope for a python3 port, I'm creting this bug to

Bug#835255: marked as done (gdc-6: std.datetime: undefined reference to dlopen/dlsym/dlclose)

Your message dated Sun, 04 Sep 2016 16:41:49 + with message-id and subject line Bug#835255: fixed in gcc-6 6.2.0-3 has caused the Debian Bug report #835255, regarding gdc-6: std.datetime: undefined reference to dlopen/dlsym/dlclose to be marked as done.

Processed: tagging 832015

Processing commands for cont...@bugs.debian.org: > # -fdebug-prefix-map is for stretch > tags 832015 + sid stretch Bug #832015 [src:libblocksruntime] libblocksruntime: FTBFS with -fdebug-prefix-map Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need

Processed: tagging 834666

Processing commands for cont...@bugs.debian.org: > # not in jessie > tags 834666 + sid stretch Bug #834666 [src:chkconfig] chkconfig: FTBFS in testing (failing tests) Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 834666:

Bug#834814: marked as done (wondershaper crashes entire system)

Your message dated Sun, 4 Sep 2016 22:09:41 +0530 with message-id

Bug#836554: [pkg-gnupg-maint] Bug#836554: gnupg - file verification leaves agent running

Control: severity 836554 normal On Sat 2016-09-03 18:40:26 -0400, Bastian Blank wrote: > Package: gnupg > Version: 2.1.15-2 > Severity: grave I'm unclear as to why this is Severity: grave -- i've reset the Severity to normal, but i'm happy to have you reset the severity with an appropriate

Processed: Re: [pkg-gnupg-maint] Bug#836554: gnupg - file verification leaves agent running

Processing control commands: > severity 836554 normal Bug #836554 [gnupg] gnupg - file verification leaves agent running Severity set to 'normal' from 'grave' -- 836554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836554 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#835581: Is my theory correct?

Control: tags -1 +moreinfo Hi, can you test whether things compile well now? Thanks, Snark on #debian-js

Bug#836670: strip-nondeterminism: leaves temporary files behind

tag 836670 + pending thanks Apologies for this. I did not spot this regression as a patch modified the testsuite to run in a temporary directory - it therefore did not pollute my working tree which — I would hope — I would have spotted. I've extended the testsuite to catch this in the future.

Processed: Re: strip-nondeterminism: leaves temporary files behind

Processing commands for cont...@bugs.debian.org: > tag 836670 + pending Bug #836670 [dh-strip-nondeterminism] strip-nondeterminism: leaves temporary files behind Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 836670:

Bug#835757: marked as done (appstream-generator: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/6/libgphobos2.a(lt4-curl.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5')

Your message dated Sun, 04 Sep 2016 16:41:49 + with message-id and subject line Bug#835757: fixed in gcc-6 6.2.0-3 has caused the Debian Bug report #835757, regarding appstream-generator: FTBFS: ld:

Bug#829640: (no subject)

> 1) It's still al just Wants, no Requires... i.e. if netfilter rules loading fails for whichever reason, the boot process will continue just normally, with networking and any daemons, that possibly require netfilter for their security, being brought up. There is a separate bug report for this:

Processed: strip-nondeterminism: leaves temporary files behind

Processing control commands: > affects -1 + src:lintian Bug #836670 [dh-strip-nondeterminism] strip-nondeterminism: leaves temporary files behind Added indication that 836670 affects src:lintian -- 836670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836670 Debian Bug Tracking System

Bug#836670: strip-nondeterminism: leaves temporary files behind

Package: dh-strip-nondeterminism Version: 0.024-1 Severity: serious Control: affects -1 + src:lintian Justification: breaks the world dh_strip_nondeterminism leaves temporary files behind, as seen in the Lintian test suite:

Bug#814183: openmpi 1.10.2 is broken on powerpc

On 04/09/2016 15:43, Emilio Pozuelo Monfort wrote: > On Fri, 12 Feb 2016 00:17:28 +0100 Emilio Pozuelo Monfort > wrote: >> On Tue, 9 Feb 2016 21:49:29 +0200 Graham Inggs wrote: >>> Petsc rebuilt successfully [1] a couple of hours ago on poulenc.d.o. [2].

Processed: Bug#820965 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 820965 pending Bug #820965 [samba-common-bin] [regression]: net usersidlist: Could not malloc sid array Could not get the user/sid list Ignoring request to alter tags of bug #820965 to the same tags previously set > thanks Stopping

Processed: tagging 835106

Processing commands for cont...@bugs.debian.org: > # not in jessie > tags 835106 + sid stretch Bug #835106 [src:fauhdlc] fauhdlc: FTBFS: expected ')' before 'istream' Added tag(s) sid and stretch. > tags 835034 + sid stretch Bug #835034 [src:bbpager] bbpager: FTBFS [amd64]: relocation

Bug#820965: marked as pending

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

Bug#836510: marked as pending

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

Processed: Bug#820965 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 820965 pending Bug #820965 [samba-common-bin] [regression]: net usersidlist: Could not malloc sid array Could not get the user/sid list Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Bug#836510 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 836510 pending Bug #836510 [src:quilt] quilt: FTBFS in testing (failing tests) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 836510:

Processed: Is my theory correct?

Processing control commands: > tags -1 +moreinfo Bug #835581 [src:node-es6-promise] node-es6-promise: FTBFS in testing (compile-modules shows usage help) Added tag(s) moreinfo. -- 835581: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835581 Debian Bug Tracking System Contact

Bug#835749: This package can be removed

This was packaged as a dependency for gitlab and recent versions of gitlab does not need it any more (it was removed from Gemfile, but debian/control was not updated). There are no other reverse dependencies, so this can be removed, once I upload a new version of gitlab which does not depend on

Processed: tagging 833950

Processing commands for cont...@bugs.debian.org: > # libasound2 1.1.2-1 not in jessie > tags 833950 + sid stretch Bug #833950 [portaudio19] libportaudio2: brltty-espeak stops working with libasound2 1.1.2-1 Added tag(s) stretch and sid. > thanks Stopping processing here. Please contact me if

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

Xavier: ping! >From Aug 31: > I don't see any activity going on this package, and it already has 2 > unaswered RC bugs (#790664 from half 2015). On Fri, 2016-09-02 at 13:11 +, Mattia Rizzolo wrote: > On Fri, Sep 02, 2016 at 03:09:29PM +0200, Svante Signell wrote: > > > > On Fri, 2016-09-02

Bug#836678: regina-normal: FTBFS: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

Source: regina-normal Version: 4.96-3 Severity: serious Your package failed to build on several release architectures: /«PKGBUILDDIR»/engine/snappea/kernel/tables.c:229:67: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing] Logs at

Processed: tagging 834242

Processing commands for cont...@bugs.debian.org: > tags 834242 + sid stretch Bug #834242 {Done: John Paul Adrian Glaubitz } [src:kcemu] kcemu: FTBFS with GCC 6 Added tag(s) stretch and sid. > thanks Stopping processing here. Please contact me if you need

Bug#822653: marked as done (loggerhead: needs to be updated for bzr 2.7.0)

Your message dated Sun, 04 Sep 2016 16:47:09 + with message-id and subject line Bug#822653: fixed in loggerhead 1.19~bzr479+dfsg-2 has caused the Debian Bug report #822653, regarding loggerhead: needs to be updated for bzr 2.7.0 to be marked as done. This

Bug#835240: marked as done (flask-script: FTBFS against pytest 3.0.0)

Your message dated Sun, 4 Sep 2016 18:42:33 +0200 with message-id and subject line closing bug has caused the Debian Bug report #835240, regarding flask-script: FTBFS against pytest 3.0.0 to be marked as done. This means that you claim that the

Processed: bug 817231 is forwarded to https://github.com/rabbitvcs/rabbitvcs/issues/127

Processing commands for cont...@bugs.debian.org: > forwarded 817231 https://github.com/rabbitvcs/rabbitvcs/issues/127 Bug #817231 {Done: Christopher Hoskin } [src:rabbitvcs] rabbitvcs: All files in home folder removed Set Bug forwarded-to-address to

Bug#835536: closed by Dominic Hargreaves <d...@earth.li> (Bug#835536: fixed in request-tracker4 4.2.13-1)

On Sat, Sep 03, 2016 at 09:18:49PM +0300, Niko Tyni wrote: > Control: found -1 4.2.13-1 > > > request-tracker4 (4.2.13-1) unstable; urgency=medium > >* Fix FTBFS with gpg 2.1 by no longer explicitly configuring the > > path to gpg (Closes: #835536) > > This doesn't seem to have worked:

Bug#836208: llvm-toolchain-3.9: stay out of testing

Le 31/08/2016 à 16:47, Emilio Pozuelo Monfort a écrit : Source: llvm-toolchain-3.9 Severity: serious This is a placeholder bug to keep llvm-toolchain-3.9 out of testing (and Stretch) for the time being, to avoid releasing Stretch with 5 LLVM versions. I'm not against releasing with 3.9 in

Bug#835037: marked as done (ceres-solver: FTBFS with eigen3 >> 3.3~beta1)

Your message dated Sun, 04 Sep 2016 13:18:43 + with message-id and subject line Bug#835037: fixed in ceres-solver 1.11.0+git20160903-1 has caused the Debian Bug report #835037, regarding ceres-solver: FTBFS with eigen3 >> 3.3~beta1 to be marked as done.

Bug#832622: marked as done (clang-3.9: Uninstallable in unstable)

Your message dated Sun, 4 Sep 2016 15:35:08 +0200 with message-id <42996ad0-7a14-a47b-e16e-5f371015d...@debian.org> and subject line now fixed has caused the Debian Bug report #832622, regarding clang-3.9: Uninstallable in unstable to be marked as done. This means that you claim that the problem

Bug#836571: jessie-pu: package rabbitvcs/0.16-1

Package: release.debian.org Severity: critical Tags: patch User: release.debian@packages.debian.org Usertags: pu The attached patch fixes bug #817231 in the rabbitvcs package. This is classified as a critical bug on the grounds that it can cause serious data loss (e.g. loss of entire home

Bug#830568: python-asyncssh: accesses the internet during build

❦ 4 septembre 2016 10:13 CEST, Chris Lamb  : >> > Oh! I thought we were discussing whether it was a bug at all […] not the >> > severity of the bug itself. >> >> This is why I think the issue should be discussed more broadly. > > To be clear, I was referring to that it was

Bug#811432: Krita no longer part of Calligra

Hi, On 04/09/16 05:42, juichenieder-deb...@yahoo.co.uk wrote: > Just found out about Krita, and thinking about giving it a try... > > > Does the fact that the latest stable version of Krita upstream (3.x) has now > split from Calligra have any bearing > on this bug? > > I.e. instead of trying

Processed: re: imapcopy: FTBFS: Error: identifier idents no member

Processing commands for cont...@bugs.debian.org: > tags 818448 +patch Bug #818448 [imapcopy] imapcopy: FTBFS: Error: identifier idents no member Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 818448:

Bug#836585: celery: FTBFS in testing (failing tests)

Package: src:celery Version: 3.1.23-5 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Bug#821347: marked as done (FTBFS on mipsel and s390x: test suite failures)

Your message dated Sun, 04 Sep 2016 10:56:40 + with message-id and subject line Bug#821347: fixed in libsecret 0.18.5-2 has caused the Debian Bug report #821347, regarding FTBFS on mipsel and s390x: test suite failures to be marked as done. This means

Processed: lldb: Please provide lldb for arm64

Processing control commands: > block 836335 by -1 Bug #836335 [src:rustc] lldb dependency cannot be satisfied on all archs 836335 was not blocked by any bugs. 836335 was not blocking any bugs. Added blocking bug(s) of 836335: 836591 -- 836335:

Bug#836587: confirm this bug

I will confirm this bug after a normal upgrade via   `apt-get update && apt-get upgrade`. Workbench opens but crashes on opening a DB after asking for the password. Linux 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64 GNU/Linux Debian GNU/Linux stretch

Bug#836597: lightspark: FTBFS on powerpc: segmentation fault during configure

Source: lightspark Version: 0.7.2+git20150512-2.1 Severity: serious Your package fails to build on powerpc: -- Found assembler: /usr/bin/nasm -- LLVM llvm-config found at: /usr/bin/llvm-config -- LLVM version: 3.6.2 Segmentation fault Logs at:

Bug#830568: python-asyncssh: accesses the internet during build

> > Oh! I thought we were discussing whether it was a bug at all […] not the > > severity of the bug itself. > > This is why I think the issue should be discussed more broadly. To be clear, I was referring to that it was regrettable — in general — that you would ignore any bug submitted against

Processed: Re: libquvi-scripts-0.9: some Youtube URLs are not working (gives 403 errors)

Processing control commands: > severity -1 important Bug #836160 [libquvi-scripts-0.9] libquvi-scripts-0.9: Youtube support is broken (gives 403 errors) Severity set to 'important' from 'serious' > retitle -1 libquvi-scripts-0.9: some Youtube URLs are not working (gives 403 > errors) Bug

Bug#836160: libquvi-scripts-0.9: some Youtube URLs are not working (gives 403 errors)

Control: severity -1 important Control: retitle -1 libquvi-scripts-0.9: some Youtube URLs are not working (gives 403 errors) On Wed, 2016-08-31 at 12:09 +0800, Paul Wise wrote: > The Youtube support appears to be broken as it gives 403 errors. Other > downloaders like youtube-dl still work

Bug#811432: Krita no longer part of Calligra

Hi, > My guess is that most of these bugs will fix themselves once 2.9 is > packaged. I think there were some attempts to fix these before, but the > package was rejected by the ftpmasters on copyright grounds - so they'll > need to be some work to sort that out. Yes, pretty much my

Bug#836611: chromium: crash after upgrade 52.0.2743.116-2 -> 53.0.2785.89-1

Package: chromium Version: 53.0.2785.89-1 Severity: grave Justification: renders package unusable Downgrading to 52.0.2743.116-2 makes it usable. All TABs "Aw Snap!" after start :( This is what I do: $ chromium --no-referrers --proxy-server=localhost:8118 --disk-cache-size=0

Bug#830414: marked as done (django-polymorphic: accesses the internet during build)

Your message dated Sun, 04 Sep 2016 07:33:33 + with message-id and subject line Bug#830414: fixed in django-polymorphic 1.0-1 has caused the Debian Bug report #830414, regarding django-polymorphic: accesses the internet during build to be marked as done.

Bug#828654: marked as done (FTBFS under Django 1.10)

Your message dated Sun, 04 Sep 2016 07:33:33 + with message-id and subject line Bug#828654: fixed in django-polymorphic 1.0-1 has caused the Debian Bug report #828654, regarding FTBFS under Django 1.10 to be marked as done. This means that you claim that

Processed: tagging 836444

Processing commands for cont...@bugs.debian.org: > # does not affect jessie > tags 836444 + sid stretch Bug #836444 [src:shogun] shogun: FTBFS with eigen3 3.3~beta2-1 Added tag(s) stretch and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 836444:

Processed: tagging 835425

Processing commands for cont...@bugs.debian.org: > # does not affect jessie > tags 835613 + sid stretch Bug #835613 [src:golang-goyaml] golang-goyaml: FTBFS: FAIL: encode_test.go:217: S.TestMarshal Added tag(s) sid and stretch. > tags 835702 + sid stretch Bug #835702 [src:seahorse-nautilus]

Bug#836595: ruby-celluloid-io: FTBFS too much often (failing tests)

Package: src:ruby-celluloid-io Version: 0.16.2-2 Severity: serious Dear maintainer: I tried to build this package in stretch with "dpkg-buildpackage -A" (which is what the "Arch: all" autobuilder would do to build it) but it failed:

Bug#836599: shark: FTBFS on mips/mipsel: test errors

Source: shark Version: 3.1.3+ds1-1 Severity: serious Your package failed to build on mips/mipsel: 95% tests passed, 8 tests failed out of 163 Logs at https://buildd.debian.org/status/package.php?p=shark=unstable Emilio

Bug#836587: mysql-workbench: Mysql-workbench opened ok but when I try to connect to db, it crashes with segfault

Package: mysql-workbench Version: 6.3.4+dfsg-3+b5 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? When I first open mysql-workbench it opens ok. But when I try to login to my databases, it crashes. * What exactly did you do (or not

Bug#822038: xine-lib-1.2: diff for NMU version 1.2.6-1.2

Control: tags 822038 + pending Dear maintainer, I've prepared an NMU for xine-lib-1.2 (versioned as 1.2.6-1.2) and uploaded it to DELAYED/1. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru xine-lib-1.2-1.2.6/debian/changelog

Processed: xine-lib-1.2: diff for NMU version 1.2.6-1.2

Processing control commands: > tags 822038 + pending Bug #822038 [src:xine-lib-1.2] xine-lib-1.2: Build arch:all+arch:any but is missing build-{arch,indep} targets Added tag(s) pending. -- 822038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822038 Debian Bug Tracking System Contact

Bug#836587: Extra Info

Hi there I thought I would attach a file showing the packages that were installed/updated during my system upgrade on Saturday.This is because, before I did the upgrade, mysql-workbench worked fine. Cheers Saturday 3 September 10:23:22 AEST 2016 [root@debiantesting vince]# apt-get dist-upgrade

Bug#836338: marked as done (grads: FTBFS with libdap 3.18.0)

Your message dated Sun, 04 Sep 2016 10:20:17 + with message-id and subject line Bug#836338: fixed in grads 2:2.1.a3-4 has caused the Debian Bug report #836338, regarding grads: FTBFS with libdap 3.18.0 to be marked as done. This means that you claim that

Bug#836588: cupt: FTBFS on armel/armhf: test failures

Source: cupt Version: 2.9.5 Severity: serious Your package failed to build on armel/armhf. Logs at https://buildd.debian.org/status/package.php?p=cupt=unstable Emilio

Bug#836589: icinga2: FTBFS on armhf/mips/mipsel

Source: icinga2 Version: 2.5.4-1 Severity: serious Hi, Your package failed to build on armhf because of test suite errors, and on mips/mipsel because of insuficient virtual memory. Logs at https://buildd.debian.org/status/package.php?p=icinga2=unstable Emilio -- System Information: Debian

Bug#818448: imapcopy: FTBFS: Error: identifier idents no member

tags 818448 +patch thanks The fix for this build failure is trivial. Patch attatched. Note: I have tested that this builds, I have not tested it beyond that. diff -Nru imapcopy-1.04/debian/changelog imapcopy-1.04/debian/changelog --- imapcopy-1.04/debian/changelog 2014-03-29

Bug#836162: prepare to remove hardening-wrapper

Control: title -1 prepare to remove hardening-wrapper bugs are now filed as https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=hardening-wrapper;users=debian-...@lists.debian.org

Bug#836670: marked as done (strip-nondeterminism: leaves temporary files behind)

Your message dated Sun, 04 Sep 2016 18:25:13 + with message-id and subject line Bug#836670: fixed in strip-nondeterminism 0.025-1 has caused the Debian Bug report #836670, regarding strip-nondeterminism: leaves temporary files behind to be marked as done.

Bug#835755: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

Control: tags -1 patch pending Because this RC bug is threatening the removal of qgis from testing, I've uploaded the attached changes to DELAYED/10 per the NMU guidelines. Please let me know if you'd like me to cancel the upload or delay it further in case you want to upload a different fix.

Bug#825815: marked as pending

tag 825815 pending thanks Hello, Bug #825815 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/pyexcelerator.git;a=commitdiff;h=ab7aea9 --- commit

Processed: Re: Bug#816063: emacs24: TLS certificate validation is silently broken

Processing commands for cont...@bugs.debian.org: > tags 816063 +unreproducible Bug #816063 [emacs24] emacs24: TLS certificate validation is silently broken Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 816063:

Bug#835755: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

On domingo, 4 de septiembre de 2016 10:53:46 P. M. ART Sebastiaan Couwenberg wrote: > On 09/04/2016 10:45 PM, Lisandro Damián Nicanor Pérez Meyer wrote: > > Passing -c0 is definitely not the way to go. Please remove the current > > upload from the delayed queue. > > I will cancel the upload if

Processed: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

Processing control commands: > tags -1 patch pending Bug #835755 [src:qwt] qwt: FTBFS: dh_makeshlibs: failing due to earlier errors Added tag(s) pending and patch. -- 835755: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835755 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#836611: chromium: crash after upgrade 52.0.2743.116-2 -> 53.0.2785.89-1

Also, I have forgot to share the exact error message I have found in /var/log/messages; my apologies: Chrome_IOThread[22183]: segfault at ba4f101fef30 ip 55e548ba7d96 sp 7f6d2a7f9100 error 5 in chromium[55e547b89000+7b32000] On Sun, 4 Sep 2016 15:02:12 +0200 (CEST) Cristian

Bug#836537: snd: FTBFS: snd-main.c:2162:24: error: macro "g_abort" passed 1 arguments, but takes just 0

On Sat, 03 Sep 2016 20:53:29 +0100 Chris Lamb wrote: > Source: snd > Version: 16.7-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

Bug#811323: marked as done (mugshot: FTBFS: ImportError: No module named 'gi')

Your message dated Sun, 04 Sep 2016 19:32:25 + with message-id and subject line Bug#811323: fixed in mugshot 0.3.1-1 has caused the Debian Bug report #811323, regarding mugshot: FTBFS: ImportError: No module named 'gi' to be marked as done. This means

Bug#834683: marked as done (mini-buildd: FTBFS too much often (failing tests))

Your message dated Sun, 04 Sep 2016 19:32:17 + with message-id and subject line Bug#834683: fixed in mini-buildd 1.0.17 has caused the Debian Bug report #834683, regarding mini-buildd: FTBFS too much often (failing tests) to be marked as done. This means

Bug#833970: marked as done (netkit-rsh: uses deprecated BSD union wait type)

Your message dated Sun, 04 Sep 2016 19:32:34 + with message-id and subject line Bug#833970: fixed in netkit-rsh 0.17-16 has caused the Debian Bug report #833970, regarding netkit-rsh: uses deprecated BSD union wait type to be marked as done. This means

Bug#822716: marked as done (firefox: FTBFS with GCC 6: 'malloc' was not declared in this scope)

Your message dated Mon, 5 Sep 2016 06:40:33 +0900 with message-id <20160904214033.w6jbd3zzz27va...@glandium.org> and subject line Re: Bug#822716: firefox: FTBFS with GCC 6: 'malloc' was not declared in this scope has caused the Debian Bug report #822716, regarding firefox: FTBFS with GCC 6:

Bug#816063: emacs24: TLS certificate validation is silently broken

tags +unreproducible thanks Rob Browning writes: > Nathaniel Smith writes: > >> And sometimes I've even had it fail on https://wrong.host.badssl.com >> after setting this (but not always). However, it always happily loads >>

Bug#835749: This package can be removed

On Sun, Sep 04, 2016 at 08:29:59PM +0530, Pirate Praveen wrote: > This was packaged as a dependency for gitlab and recent versions of > gitlab does not need it any more (it was removed from Gemfile, but > debian/control was not updated). > > There are no other reverse dependencies, so this can be

Bug#835755: qwt: FTBFS: dh_makeshlibs: failing due to earlier errors

On 09/04/2016 10:45 PM, Lisandro Damián Nicanor Pérez Meyer wrote: > Passing -c0 is definitely not the way to go. Please remove the current > upload from the delayed queue. I will cancel the upload if you confirm to upload a different fix to prevent the testing autoremoval. I do not agree that

Bug#836611: chromium: crash after upgrade 52.0.2743.116-2 -> 53.0.2785.89-1

Weird...I have the same problem with 52.0.2743.116-2 and it happened a few minutes ago when I tried to open multiple tabs at once. I'm using Debian testing 64-bit, fully updated. On Sun, 4 Sep 2016 15:02:12 +0200 (CEST) Cristian Ionescu-Idbohrn wrote: >

Bug#836510: marked as done (quilt: FTBFS in testing (failing tests))

Your message dated Sun, 04 Sep 2016 19:00:12 + with message-id and subject line Bug#836510: fixed in quilt 0.63-4 has caused the Debian Bug report #836510, regarding quilt: FTBFS in testing (failing tests) to be marked as done. This means that you claim

  1   2   >