Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita

On 09/02/2016 05:15 AM, Raphaël Halimi wrote: > This bug certainly has the same root cause as #826261, as it has the > same symptoms: it doesn't appear with Adwaita theme, and it only appear > when the window is maximized. Can you people *please* stop filing bug reports telling us that MATE has

Processed: Re: din: FTBFS with GCC 6: narrowing conversion

Processing control commands: > tags -1 patch Bug #811778 [din] din: FTBFS with GCC 6: narrowing conversion Added tag(s) patch. -- 811778: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

Hola Maximiliano! On Thu, Sep 1, 2016 at 6:20 AM, Maximiliano Curia wrote: > > ¡Hola Ismael! > > El 2016-08-30 a las 01:13 -0300, Ismael escribió: >> >> Package: akregator Version: 4:16.04.3-1 Severity: grave Justification: causes non-serious data loss > > >> * What led up to

Bug#836352: Scrollbar can't go to the bottom with a theme other than Adwaita

Package: caja Version: 1.14.2-1 Severity: grave This bug certainly has the same root cause as #826261, as it has the same symptoms: it doesn't appear with Adwaita theme, and it only appear when the window is maximized. When a scrollbar is displayed, it can't be dragged all the way to the bottom,

Bug#836260: marked as done (libgnuradio-radar3.7.8 and libgnuradio-radar3.7.10: error when trying to install together)

Your message dated Fri, 02 Sep 2016 01:33:46 + with message-id and subject line Bug#836260: fixed in gr-radar 0.0.0.20160615-3 has caused the Debian Bug report #836260, regarding libgnuradio-radar3.7.8 and libgnuradio-radar3.7.10: error when trying to

Bug#810907: repsnapper: FTBFS on ppc64el: termios problems

On Sun, 14 Feb 2016 18:39:49 +0100 Andreas Beckmann wrote: > Followup-For: Bug #810907 > Control: found -1 2.4a0-1 > Control: severity -1 serious > Control: tag -1 patch > > the same issue happens on powerpc > >

Bug#836347: gkrellweather: weather.noaa.gov has been shut down

Sorry, On Fri, 02 Sep 2016 01:18:06 +0200 Roland Hieber wrote: > weather.noaa.gov has been shut down [0] [0]: http://www.nws.noaa.gov/om/notification/scn16-16wngccb.htm

Bug#834677: marked as done (refcard: FTBFS in testing (xelatex compilation failed))

Your message dated Thu, 01 Sep 2016 23:21:28 + with message-id and subject line Bug#834677: fixed in refcard 9.0.3 has caused the Debian Bug report #834677, regarding refcard: FTBFS in testing (xelatex compilation failed) to be marked as done. This means

Bug#836347: gkrellweather: weather.noaa.gov has been shut down

Package: gkrellweather Version: 2.0.8-2 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, weather.noaa.gov has been shut down [0], and the METAR data is now available on a different site. This patch works for me: - snip

Bug#834677: refcard: FTBFS in testing (xelatex compilation failed)

On 2016-09-01 21:10, Holger Wansing wrote: > Martin: I fear, there is another upload needed :-( No problem! Anyway, I added you to Uploaders :~)

Bug#817488: marked as done (gsfonts: Removal of debhelper compat 4)

Your message dated Thu, 01 Sep 2016 22:20:17 + with message-id and subject line Bug#817488: fixed in gsfonts 1:8.11+urwcyr1.0.7~pre44-4.3 has caused the Debian Bug report #817488, regarding gsfonts: Removal of debhelper compat 4 to be marked as done. This

Bug#835987: marked as done (2.0.5 breaks dbc_dbname preseeding support)

Your message dated Thu, 01 Sep 2016 22:19:24 + with message-id and subject line Bug#835987: fixed in dbconfig-common 2.0.6 has caused the Debian Bug report #835987, regarding 2.0.5 breaks dbc_dbname preseeding support to be marked as done. This means that

Bug#835075: [Reproducible-builds] Bug#835075: libmail-gnupg-perl: FTBFS: Failed 1/10 test programs. 0/4 subtests failed.

On Thu, 01 Sep 2016 16:00:52 -0400, Daniel Kahn Gillmor wrote: > On Thu 2016-09-01 10:52:47 -0400, gregor herrmann wrote: > > On Tue, 30 Aug 2016 08:05:14 -0400, Daniel Kahn Gillmor wrote: > > Maybe we should think about this for the test suite temporarily. > > Or maybe we can trick gpg-agent

Processed (with 1 error): Merge kytea bugs

Processing commands for cont...@bugs.debian.org: > merge 799805 804356 Bug #799805 [src:kytea] kytea: Problem with upcoming new version of liblinear Unable to merge bugs because: blocks of #804356 is '' not '803680' Failed to merge 799805: Did not alter merged bugs. > End of message, stopping

Bug#836338: grads: FTBFS with libdap 3.18.0

Source: grads Version: 2:2.1.a3-3 Severity: serious Tags: upstream Justification: make the package in question unusable or mostly so Control: block 836192 by -1 Dear Maintainer, As mentioned in the libdap transition bugreport (#836192), grads fails to build with libdap 3.18.0. The buildlogs

Processed: grads: FTBFS with libdap 3.18.0

Processing control commands: > block 836192 by -1 Bug #836192 [release.debian.org] transition: libdap 836192 was blocked by: 836173 836187 836192 was not blocking any bugs. Added blocking bug(s) of 836192: 836338 -- 836192: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836192 836338:

Processed: [/sid] Fix dbc_dbname preseeding regression caused by the commit 4b3d1b

Processing commands for cont...@bugs.debian.org: > tag 835987 pending Bug #835987 [dbconfig-common] 2.0.5 breaks dbc_dbname preseeding support Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 835987:

Bug#835987: [/sid] Fix dbc_dbname preseeding regression caused by the commit 4b3d1b

tag 835987 pending thanks Date: Thu Sep 1 21:51:32 2016 +0200 Author: Paul Gevers Commit ID: d2ddb2b31644ed32fa1fcf70b33507c2550a01bd Commit URL: https://anonscm.debian.org/cgit/collab-maint/dbconfig-common.git;a=commitdiff;h=d2ddb2b31644ed32fa1fcf70b33507c2550a01bd Patch

Bug#835250: marked as pending

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

Processed: Bug#835250 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 835250 pending Bug #835250 [src:sqlobject] FTBFS against pytest 3.0.0 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 835250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835250

Bug#835075: [Reproducible-builds] Bug#835075: libmail-gnupg-perl: FTBFS: Failed 1/10 test programs. 0/4 subtests failed.

On Thu 2016-09-01 10:52:47 -0400, gregor herrmann wrote: > On Tue, 30 Aug 2016 08:05:14 -0400, Daniel Kahn Gillmor wrote: > Maybe we should think about this for the test suite temporarily. > Or maybe we can trick gpg-agent into working during build / in a > chroot somehow. And stopping it

Processed: Bug#833968: csh: uses deprecated BSD union wait type

Processing control commands: > severity -1 serious Bug #833968 [csh] csh: uses deprecated BSD union wait type Severity set to 'serious' from 'important' -- 833968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#836335: lldb dependency cannot be satisfied on all archs

Package: src:rustc Version: 1.10.0+dfsg1-3 Severity: serious Tags: sid stretch excuses: 32 days old (needed 5 days) rust-lldb/arm64 unsatisfiable Depends: lldb Valid candidate the package doesn't migrate, you should only depend on lldb on architectures where it exists.

Processed: Re: dbconfig-common: autopkg test fails with 2.0.5

Processing control commands: > severity -1 normal Bug #835981 [dbconfig-common] dbconfig-common: autopkg test fails with 2.0.5 Severity set to 'normal' from 'serious' -- 835981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835981 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#834677: refcard: FTBFS in testing (xelatex compilation failed)

Hi, victory wrote: > On Wed, 31 Aug 2016 01:41:03 -0400 > Jeremy Bicha wrote: > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/refcard.html > > > ! I can't find file `IPAPMincho'. > > ! I can't find file `IPAPGothic'. > > apparently new Depends

Bug#835981: dbconfig-common: autopkg test fails with 2.0.5

control: severity -1 normal On Mon, 29 Aug 2016 20:41:53 +0200 Paul Gevers wrote: > To prevent migration of the current package before I understand why > and determine it to be ok or not, I file this bug. So the issue is not severe. What happens is that MariaDB and MySQL

Processed: Re: Bug#835987:

Processing control commands: > retitle -1 2.0.5 breaks dbc_dbname preseeding support Bug #835987 [dbconfig-common] 2.0.5 breaks SQLite(3) support Changed Bug title to '2.0.5 breaks dbc_dbname preseeding support' from '2.0.5 breaks SQLite(3) support'. -- 835987:

Bug#835987:

control: retitle -1 2.0.5 breaks dbc_dbname preseeding support On 30-08-16 21:41, Paul Gevers wrote: > Just for the record, the issue is that with 2.0.5 dbconfig support > dbadmin-less setup for MariaDB/MySQL and PostgreSQL, but the > implementation broke SQLite support. > > The issue is in line

Bug#835078: this is a trivial test failure

Control: severity -1 important This is caused by graphicsmagick version in debian being strange. This test is disabled in last upload. signature.asc Description: OpenPGP digital signature

Processed: this is a trivial test failure

Processing control commands: > severity -1 important Bug #835078 [src:ruby-mini-magick] ruby-mini-magick: FTBFS: ./spec/lib/mini_magick_spec.rb:34 # MiniMagick.cli_version returns GraphicsMagick's version Severity set to 'important' from 'serious' -- 835078:

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

Your message dated Thu, 01 Sep 2016 18:48:57 + with message-id and subject line Bug#828650: fixed in django-markupfield 1.4.0-2 has caused the Debian Bug report #828650, regarding FTBFS under Django 1.10 to be marked as done. This means that you claim

Bug#780429: marked as done (snmp-mibs-downloader: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/mibrfcs/*)

Your message dated Thu, 01 Sep 2016 18:50:09 + with message-id and subject line Bug#780429: fixed in snmp-mibs-downloader 1.1+nmu1 has caused the Debian Bug report #780429, regarding snmp-mibs-downloader: postinst uses /usr/share/doc content (Policy

Processed: [bts-link] source package src:golang-github-hashicorp-go-reap

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package > src:golang-github-hashicorp-go-reap > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Processed: [bts-link] source package python-pyotp

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package python-pyotp > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Processed: [bts-link] source package src:ostinato

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:ostinato > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

Bug#836327: gsequencer: FTBFS on mips and powerpc: ags_functional_audio_test segmentation fault

Source: gsequencer Version: 0.7.62-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The latest builds of gsequencer for mips and powerpc both failed because ags_functional_audio_test segfaulted:

Bug#836326: gsequencer: FTBFS on i386: ags_channel_test segmentation fault

Source: gsequencer Version: 0.7.62-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The latest i386 build of gsequencer failed because ags_channel_test crashed. Could you please take a look? Thanks! PASS: ags_thread_test PASS:

Bug#834963: marked as done (ruby-protected-attributes: FTBFS too much often (failing tests))

Your message dated Thu, 01 Sep 2016 16:30:41 + with message-id and subject line Bug#834963: fixed in ruby-protected-attributes 1.1.3-2 has caused the Debian Bug report #834963, regarding ruby-protected-attributes: FTBFS too much often (failing tests) to be

Bug#835465: marked as done (python-apt: FTBFS: AptKeyError: recv from 'hkp://localhost:19191' failed for '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553')

Your message dated Thu, 01 Sep 2016 16:29:47 + with message-id and subject line Bug#835465: fixed in python-apt 1.1.0~beta5 has caused the Debian Bug report #835465, regarding python-apt: FTBFS: AptKeyError: recv from 'hkp://localhost:19191' failed for

Bug#836308: marked as done (librasterlite2: FTBFS: geotiff.h:35:24: fatal error: geo_config.h: No such file or directory)

Your message dated Thu, 01 Sep 2016 16:25:06 + with message-id and subject line Bug#836308: fixed in librasterlite2 1.0.0~rc0+devel1-4 has caused the Debian Bug report #836308, regarding librasterlite2: FTBFS: geotiff.h:35:24: fatal error: geo_config.h: No

Bug#835695: [Android-tools-devel] Bug#835695: android-platform-development: FTBFS: ld: cannot find -lETC1

Hi, I must apologize here, I mixed with src:android-platform-development with src:android-platform-dalvik. Either way, the issue was still multilib, and Kai-Chung Yan has fixed that and filed a RFS for this package. Version r55 should fix it once that is uploaded. Regards, Chirayu Desai On

Processed: Re: Bug#836308: librasterlite2: FTBFS: geotiff.h:35:24: fatal error: geo_config.h: No such file or directory

Processing control commands: > tags -1 pending Bug #836308 [src:librasterlite2] librasterlite2: FTBFS: geotiff.h:35:24: fatal error: geo_config.h: No such file or directory Added tag(s) pending. -- 836308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836308 Debian Bug Tracking System

Bug#836308: librasterlite2: FTBFS: geotiff.h:35:24: fatal error: geo_config.h: No such file or directory

Control: tags -1 pending Hi Chris, Thanks for reporting this issue. The problem became clear from the full buildlog: | #include configure:4832: result: no configure:4832: checking for geotiff.h configure:4832: result: no configure:4846: error: 'libgeotiff' is required but the header

Bug#836320: mactelnet: CVE-2016-7115

Source: mactelnet Version: 0.4.0-1 Severity: grave Tags: security upstream Hi, the following vulnerability was published for mactelnet. CVE-2016-7115[0]: | Buffer overflow in the handle_packet function in mactelnet.c in the | client in MAC-Telnet 0.4.3 and earlier allows remote TELNET servers

Bug#835353: pari: diff for NMU version 2.7.6-1.1

On Thu, 01 Sep 2016 16:57:57 +0200, gregor herrmann wrote: > > I would not mind if it was delayed until Sep 6, so I had a change > > to review it. > I rescheduled it to 5-day which should be the 6th September, hope > that's ok. Ok, after this reply: | > reschedule pari_2.7.6-1.1_amd64.changes

Bug#835353: pari: diff for NMU version 2.7.6-1.1

On Thu, 01 Sep 2016 10:16:58 +0200, Bill Allombert wrote: > > I've prepared an NMU for pari (versioned as 2.7.6-1.1) and > > uploaded it to DELAYED/5. Please feel free to tell me if I > > should delay it longer. > Thanks a lot Gregorr, this has been very sudden. This is a major > API change which

Bug#835075: [Reproducible-builds] Bug#835075: libmail-gnupg-perl: FTBFS: Failed 1/10 test programs. 0/4 subtests failed.

On Tue, 30 Aug 2016 08:05:14 -0400, Daniel Kahn Gillmor wrote: [original log:] > > You tried to plan twice at t/30.inline-decrypt.t line 30. > > # Looks like you planned 5 tests but ran 1. > > # Looks like your test exited with 2 just after 1. > > t/30.inline-decrypt.t > > 1..5 >

Processed: severity of 665001 is serious

Processing commands for cont...@bugs.debian.org: > # libmime-tools-perl upload to unstable dropped now Provides > severity 665001 serious Bug #665001 [debbugs] debbugs: depends-on-obsolete-package libmime-perl Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please

Bug#834980: cargo: FTBFS in testing (linking error)

reopen 834980 severity 834980 important thanks this issue still exists. and can be seen when you have more than one argument in LDFLAGS (separated by a space). Removing the quoting is not fixing it ... originally seen here: https://launchpad.net/ubuntu/+source/cargo/0.11.0-2

Bug#836308: librasterlite2: FTBFS: geotiff.h:35:24: fatal error: geo_config.h: No such file or directory

Source: librasterlite2 Version: 1.0.0~rc0+devel1-3 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, librasterlite2 fails to build from source

Bug#836307: czmq fails to build with glibc-2.24

Package: src:czmq Version: 3.0.2-9 Severity: serious Tags: sid stretch libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./src -I./include -pedantic -Werror -Wall -Wc++-compat -D_GNU_SOURCE -DLINUX -D_REENTRANT -D_THREAD_SAFE -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=.

Bug#824402: Forwarded upstream

Hi, I managed to build the latest upstream version of sra-toolkit 2.7.0. I made sure that the vschema files will be found but since I've got $ latf-load --quality PHRED_33 -o test /usr/share/doc/python-biopython-doc/Tests/Quality/sanger_93.fastq 2016-09-01T13:27:09 latf-load.2.7 warn:

Processed: Re: cargo: FTBFS in testing (linking error)

Processing commands for cont...@bugs.debian.org: > reopen 834980 Bug #834980 {Done: Luca Bruno } [src:cargo] cargo: FTBFS in testing (linking error) 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to

Bug#836259: [pkg-gnupg-maint] Bug#836259: gnupg2: accesses the internet during build

Werner Koch wrote: > I think it is okay to run that test only in maintainer-mode (configure > --enable-maintainer-mode). Good idea :) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#835717: marked as done (sosi2osm: FTBFS: node.cpp:54:31: error: 'max' was not declared in this scope)

Your message dated Thu, 01 Sep 2016 12:35:25 + with message-id and subject line Bug#835717: fixed in sosi2osm 1.0.0-3 has caused the Debian Bug report #835717, regarding sosi2osm: FTBFS: node.cpp:54:31: error: 'max' was not declared in this scope to be

Bug#811912: marked as done (tandem-mass: FTBFS with GCC 6: declared in this scope)

Your message dated Thu, 1 Sep 2016 13:07:14 +0200 with message-id <20160901110714.glplnstet7yi772a@roma> and subject line [done] tandem-mass: FTBFS with GCC 6: declared in this scope has caused the Debian Bug report #811912, regarding tandem-mass: FTBFS with GCC 6: declared in this scope to be

Bug#833965: tcsh: uses deprecated BSD union wait type

> On Thu, 1 Sep 2016 12:51:30 +0200, Aurelien Jarno > said: > bug to serious. If you don't have time to fix this bug, I can do a > non-maintainer upload with the patch which is in the bug log. Salut Aurelien, feel free to do a NMU. -- regards Thomas

Processed: Bug#833965: tcsh: uses deprecated BSD union wait type

Processing control commands: > severity -1 serious Bug #833965 [tcsh] tcsh: uses deprecated BSD union wait type Severity set to 'serious' from 'important' -- 833965: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#836198: marked as done (srst2: qsub_srst2.py SyntaxError (missing #!))

Your message dated Thu, 01 Sep 2016 10:39:40 + with message-id and subject line Bug#836198: fixed in srst2 0.2.0-2 has caused the Debian Bug report #836198, regarding srst2: qsub_srst2.py SyntaxError (missing #!) to be marked as done. This means that you

Processed: Re: insighttoolkit4: FTBFS: itkTriangleHelperPython.cpp:5836:65: error: no matching function for call to

Processing control commands: > forwarded -1 https://issues.itk.org/jira/browse/ITK-3466 Bug #835761 [src:insighttoolkit4] insighttoolkit4: FTBFS: itkTriangleHelperPython.cpp:5836:65: error: no matching function for call to 'itk::TriangleHelper >::TriangleHelper()' Set Bug

Processed: forcibly merging 835738 835744

Processing commands for cont...@bugs.debian.org: > forcemerge 835738 835744 Bug #835738 [src:kdepim] kdepim: FTBFS: dh_install: missing files, aborting Bug #835744 [src:kdepim] kdepim: FTBFS: dh_install: Cannot find (any matches for) "usr/share/appdata/org.kde.akregator.appdata.xml" (tried in

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

> Thanks for the report. I can't reproduce the issue here, Hi, I'm subscribed to this bug, haven't yet made a trace, but hope this helps: - when akregator is started, and then closed without opening any news item, it will close fine, 100% reproducible - as soon as any news item has been read,

Bug#836011: akregator: Akregator keep crashing at exit, sometimes do not save recent feeds

¡Hola Ismael! El 2016-08-30 a las 01:13 -0300, Ismael escribió: Package: akregator Version: 4:16.04.3-1 Severity: grave Justification: causes non-serious data loss * What led up to the situation? Since a recent upgrade (less than a month ago). After reading a feed when closing

Bug#836259: [pkg-gnupg-maint] Bug#836259: gnupg2: accesses the internet during build

On Thu, 1 Sep 2016 09:12, la...@debian.org said: > Whilst gnupg2 builds successfully on unstable/amd64, according to > Debian Policy 4.9 packages may not attempt network access during That is due to dirmngr/t-dns-stuff which for obviius reasons needs to go out. However, I think it is okay to

Processed: Forwarded to upstream

Processing commands for cont...@bugs.debian.org: > forwarded 835078 https://github.com/minimagick/minimagick/issues/377 Bug #835078 [src:ruby-mini-magick] ruby-mini-magick: FTBFS: ./spec/lib/mini_magick_spec.rb:34 # MiniMagick.cli_version returns GraphicsMagick's version Set Bug

Processed: gnupg2 should declare python3-apt breaks as well

Processing commands for cont...@bugs.debian.org: > reopen 835465 Bug #835465 [src:python-apt] python-apt: FTBFS: AptKeyError: recv from 'hkp://localhost:19191' failed for '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553' Bug 835465 is not marked as done; doing nothing. > thanks Stopping processing

Bug#836256: marked as done (*** Error in `/usr/lib/qgis/crssync': double free or corruption (fasttop): 0x810b61e0 ***)

Your message dated Thu, 1 Sep 2016 09:33:24 +0200 with message-id <6e241351-642d-1fd3-b6d7-80d53c67c...@xs4all.nl> and subject line Re: Bug#836256: *** Error in `/usr/lib/qgis/crssync': double free or corruption (fasttop): 0x810b61e0 *** has caused the Debian Bug report #836256, regarding ***

Bug#836260: libgnuradio-radar3.7.8 and libgnuradio-radar3.7.10: error when trying to install together

Package: libgnuradio-radar3.7.10,libgnuradio-radar3.7.8 Version: libgnuradio-radar3.7.10/0.0.0.20160615-2 Version: libgnuradio-radar3.7.8/0.0.0.20160615-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2016-09-01 Architecture: amd64 Distribution: sid Hi,

Processed (with 1 error): Re: Bug#836256: *** Error in `/usr/lib/qgis/crssync': double free or corruption (fasttop): 0x810b61e0 ***

Processing commands for cont...@bugs.debian.org: > reopen 836256 Bug #836256 {Done: Sebastiaan Couwenberg } [qgis-providers] *** Error in `/usr/lib/qgis/crssync': double free or corruption (fasttop): 0x810b61e0 *** Bug reopened Ignoring request to alter fixed versions of bug

Bug#834843: marked as done (ruby-doorkeeper: CVE-2016-6582)

Your message dated Thu, 01 Sep 2016 07:19:23 + with message-id and subject line Bug#834843: fixed in ruby-doorkeeper 4.2.0-3 has caused the Debian Bug report #834843, regarding ruby-doorkeeper: CVE-2016-6582 to be marked as done. This means that you claim

Bug#836256: marked as done (*** Error in `/usr/lib/qgis/crssync': double free or corruption (fasttop): 0x810b61e0 ***)

Your message dated Thu, 1 Sep 2016 09:08:08 +0200 with message-id <0ec75ba7-61dc-00c8-e5c8-e232137a8...@xs4all.nl> and subject line Re: Bug#836256: *** Error in `/usr/lib/qgis/crssync': double free or corruption (fasttop): 0x810b61e0 *** has caused the Debian Bug report #836256, regarding ***

Processed: Re: Bug#836256: *** Error in `/usr/lib/qgis/crssync': double free or corruption (fasttop): 0x810b61e0 ***

Processing commands for cont...@bugs.debian.org: > notfound 836256 qgis/2.14.6+dfsg-1~exp1 Bug #836256 [qgis-providers] *** Error in `/usr/lib/qgis/crssync': double free or corruption (fasttop): 0x810b61e0 *** No longer marked as found in versions qgis/2.14.6+dfsg-1~exp1. > thanks Stopping