Bug#807805: vlc: Crash upon startup

Package: vlc Version: 2.2.1-5+b1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After a recent system upgrade in Debian Testing, `vlc` cannot start

Bug#750904: Build on arm*

Hey George, you can close that bug here, too ;) scidavis has successfully build on arm*. I don't want to do it, because it's your package ;) Greetings Patrick

Bug#807502: gcc-avr: Missing support for atxmega

Hi, I've now uploaded a new version of avr-libc with the new names on those files. I'll also update binutils to declear that it wont work with older avr-libc. On Fri, Dec 11, 2015 at 7:56 PM, Hakan Ardo wrote: > Hi, > the file you want is crtx384d3.o and not crtatxmega384d3.o

Bug#807502: marked as done (gcc-avr: Missing support for atxmega384d3 since last upload)

Your message dated Sun, 13 Dec 2015 09:52:17 + with message-id and subject line Bug#807502: fixed in binutils-avr 2.25+Atmel3.5.0-2 has caused the Debian Bug report #807502, regarding gcc-avr: Missing support for atxmega384d3 since last upload to be marked

Bug#807805: vlc: Crash upon startup

​I realized that vlc only crashes in my i3wm setup, but does not crash if started from the KDE5 environment. ​

Bug#783108: marked as done (file: OOM and/or segfault)

Your message dated Sun, 13 Dec 2015 11:35:03 +0200 with message-id <20151213093503.GA24129@tunkki> and subject line closing has caused the Debian Bug report #783108, regarding file: OOM and/or segfault to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#805226: marked as done (praw: FTBFS: ImportError: No module named betamax)

Your message dated Sun, 13 Dec 2015 10:11:23 + with message-id and subject line Bug#805226: fixed in praw 3.3.0-1 has caused the Debian Bug report #805226, regarding praw: FTBFS: ImportError: No module named betamax to be marked as done. This means that

Bug#807564: digikam: FTBFS, cannot find Marble

Hello List, I'm looking into this aswell, since I want to use digikam again and got some free time to fix it. I hope I can provide a source-patch in the next few days that allows the currently packaged version of digikam to build again. In case I get it to work, where do I send the patch? It

Bug#807805: vlc: Crash upon startup

calling `vlc --no-qt-system-tray` will start vlc and is an effective workaround. Best, Hörmet He who is worthy to receive his days and nights is worthy to receive all else from you (and me). -- The Prophet, Gibran Kahlil

Processed: Re: Bug#807805: vlc: Crash upon startup

Processing control commands: > severity -1 important Bug #807805 [vlc] vlc: Crash upon startup Severity set to 'important' from 'grave' > tags -1 + moreinfo Bug #807805 [vlc] vlc: Crash upon startup Added tag(s) moreinfo. -- 807805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807805 Debian

Bug#807805: vlc: Crash upon startup

Control: severity -1 important Control: tags -1 + moreinfo On 2015-12-13 03:58:37, Hormet Yiltiz wrote: > Package: vlc > Version: 2.2.1-5+b1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where

Processed: severity of 807128 is normal, severity of 807867 is normal, tagging 798749, tagging 801851 ...

Processing commands for cont...@bugs.debian.org: > severity 807128 normal Bug #807128 {Done: Emilio Pozuelo Monfort } [release.debian.org] nmu: gcc-5_5.3.0-3 Severity set to 'normal' from 'serious' > severity 807867 normal Bug #807867 [release.debian.org] nmu: all packages

Processed: severity of 805817 is normal

Processing commands for cont...@bugs.debian.org: > severity 805817 normal Bug #805817 [ftp.debian.org] RM: instanbul - dead upstream, depends on gstreamer 0.10 Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 805817:

Bug#784382: marked as done (ugene: Harcodes dependencies on transitional packages)

Your message dated Mon, 14 Dec 2015 05:22:41 + with message-id and subject line Bug#784382: fixed in ugene 1.19.0+dfsg-1 has caused the Debian Bug report #784382, regarding ugene: Harcodes dependencies on transitional packages to be marked as done. This

Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

On 2015-12-12 Russ Allbery wrote: [...] > > when starting gnubg it uses 100% of one cpu core and then apparently > > hangs with no output and without starting the gui. > So, I'm not sure what's going on here, but it seems to be some sort of > weird bug in libgnutls/libtasn1.

Bug#803300: prepare for giflib5

On Wed, 28 Oct 2015 16:02:40 +0100 Matthias Klose wrote: > For the latter two options, please see a patch at > http://launchpadlibrarian.net/222944251/openscenegraph_3.2.1-7ubuntu2_3.2.1-7ubuntu3.diff.gz Upstream has fixed the giflib5 support a bit differently [0][1]. The attached debdiff uses

Bug#807250: marked as done (fretsonfire-game: Game fail to start: obsolete function called)

Your message dated Sun, 13 Dec 2015 16:51:55 + with message-id and subject line Bug#807250: fixed in fretsonfire 1.3.110.dfsg2-2 has caused the Debian Bug report #807250, regarding fretsonfire-game: Game fail to start: obsolete function called to be marked

Bug#799761: marked as done (python-nmap: FTBFS: IOError: [Errno 2] No such file or directory: 'scanme_output.xml')

Your message dated Sun, 13 Dec 2015 13:20:49 + with message-id and subject line Bug#799761: fixed in python-nmap 0.5.0-1-1 has caused the Debian Bug report #799761, regarding python-nmap: FTBFS: IOError: [Errno 2] No such file or directory:

Bug#806246: cmucl: FTBFS (missing build-depends)

Hello Santiago, > Seems like a missing Build-Depends on hardening-includes, the package > containing /usr/share/hardening-includes/hardening.make, so it > should be quite easy to fix. Turns out it's not so easy after all, I'm still working on it... > BTW: I wonder why this package does not

Bug#799997: marked as done (pyroma: FTBFS: ERROR: invocation failed (exit code 1))

Your message dated Sun, 13 Dec 2015 13:35:00 + with message-id and subject line Bug#77: fixed in pyroma 2.0.0b2-1 has caused the Debian Bug report #77, regarding pyroma: FTBFS: ERROR: invocation failed (exit code 1) to be marked as done. This

Bug#805221: marked as done (picard: FTBFS: ImportError: No module named PyQt4)

Your message dated Sun, 13 Dec 2015 12:34:42 + with message-id and subject line Bug#805221: fixed in picard 1.3.2-3 has caused the Debian Bug report #805221, regarding picard: FTBFS: ImportError: No module named PyQt4 to be marked as done. This means that

Processed: tagging 807492

Processing commands for cont...@bugs.debian.org: > tags 807492 + pending Bug #807492 [src:libmath-bigint-gmp-perl] libmath-bigint-gmp-perl: FTBFS on 32 bit platforms Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 807492:

Processed: tagging 807492

Processing commands for cont...@bugs.debian.org: > tags 807492 - pending Bug #807492 [src:libmath-bigint-gmp-perl] libmath-bigint-gmp-perl: FTBFS on 32 bit platforms Ignoring request to alter tags of bug #807492 to the same tags previously set > thanks Stopping processing here. Please contact

Bug#803300: prepare for giflib5

Hi all, 2015-12-13 15:33 GMT+00:00 Sebastiaan Couwenberg : > On Wed, 28 Oct 2015 16:02:40 +0100 Matthias Klose wrote: >> For the latter two options, please see a patch at >> http://launchpadlibrarian.net/222944251/openscenegraph_3.2.1-7ubuntu2_3.2.1-7ubuntu3.diff.gz > >

Bug#807675: More failures apparently unrelated to "SCU Failed: 0006:0213 Data dictionary missing"

Using the latest version of DCMTK, I'm unable to reproduce the error in a freshly-updated sid pbuilder running on jessie, so the following diagnosis is a bit of a guesswork. The "Address already in use" message points to an already-running DICOM server on port 2, which prohibits running the

Processed: Re: camorama cannot take pictures

Processing commands for cont...@bugs.debian.org: > severity 800586 important Bug #800586 [camorama] camorama cannot take pictures Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 800586:

Bug#800586: camorama cannot take pictures

severity 800586 important thanks Hi, > package: camorama > version: 0.19-3 > severity: grave > reason: fails its primary functionality > > It fails with an error message "Cannot create directory ~/Webcam_Picture > s" > > Same message after manually creating the directory. Taking pictures is

Bug#800216: Fwd: gniall: diff for NMU version 0.7.1-7.1

Hi, I uploaded a NMU to 10-day/delay queue. Feel free to cancel this upload if needed. The debian/changelog is: * Non-maintainer upload. * Update DH level to 9 to avoid a FTBFS. (Closes: #800216) * debian/compat: updated to 9. * debian/control: - Added the ${misc:Depends} variable to

Processed: tagging 807735

Processing commands for cont...@bugs.debian.org: > tags 807735 + sid stretch Bug #807735 [src:gmpc-plugins] gmpc-plugins: FTBFS: libmpd-internal.h:210:10: error: expected identifier or '(' before '__extension__' Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me

Processed: Fix "Can't find marble" FTBFS [patch]

Processing control commands: > tags -1 patch Bug #807564 [src:digikam] digikam: FTBFS: Could not find a package configuration file provided by "Marble" Added tag(s) patch. -- 807564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807564 Debian Bug Tracking System Contact

Bug#807564: Fix "Can't find marble" FTBFS [patch]

Control: tags -1 patch Hi List, I've tried to reproduce the build failure and it turns out that the FindMarble.cmake file is in a path that is not in the default cmake module search path. If the search path is passed to cmake with EXTRA_CMAKE_ARGS, digikam compiles successfully again. Also the

Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

The patch has not been applied because it is not clear it is correct There is a thread that starts at [1] and ended inconclusively at [2] It's unfortunate that the number of people who understand power memory ordering issues at the level required can probably be counted on one hand. But I don't

Processed: clone hardening-wrapper issue to get nmu's done

Processing commands for cont...@bugs.debian.org: > clone 801597 -1 Bug #801597 [src:hardening-wrapper] PIE and stack protection appear missing since update to GCC-5 Bug 801597 cloned as bug 807867 > reassign -1 release.debian.org Bug #807867 [src:hardening-wrapper] PIE and stack protection

Processed: tagging 807657

Processing commands for cont...@bugs.debian.org: > tags 807657 + sid stretch Bug #807657 [src:dvdauthor] dvdauthor: FTBFS: compat.h:141:8: error: expected identifier or '(' before '__extension__' Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need

Processed: tagging 807609

Processing commands for cont...@bugs.debian.org: > tags 807609 + sid stretch Bug #807609 [src:spatial4j] spatial4j: FTBFS: [ERROR] The specified user settings file does not exist: /etc/maven2/settings-debian.xml Added tag(s) stretch and sid. > thanks Stopping processing here. Please contact me

Bug#807867: nmu: all packages built without GCC 5 and hardening-wrapper

hardening-wrapper 1.28+nmu1 is supposed to fix hardening-wrapper, however binNMUs for all packages build-depending on hardening-wrapper, which got built (either uploaded or binNMUed) after GCC 5 became the default have to be successfully done.

Bug#803293: marked as done (prepare for giflib5)

Your message dated Sun, 13 Dec 2015 19:23:09 + with message-id and subject line Bug#803293: fixed in xplanet 1.3.0-3 has caused the Debian Bug report #803293, regarding prepare for giflib5 to be marked as done. This means that you claim that the problem

Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

Control: tag -1 - pending On Mon, 14 Dec 2015 08:05:22 +1100, Ian Wienand wrote: > The patch has not been applied because it is not clear it is correct > > There is a thread that starts at [1] and ended inconclusively at [2] > > It's unfortunate that the number of people who understand power

Processed: Re: Bug#728955: libatomic-ops: diff for NMU version 7.4.2-1.2

Processing control commands: > tag -1 - pending Bug #728955 [src:libatomic-ops] FTBFS on powerpc: FAIL: test_stack Removed tag(s) pending. -- 728955: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728955 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: this is broken.

Processing commands for cont...@bugs.debian.org: > severity 765419 serious Bug #765419 [mumble-django] mumble-django: wont install , broken is useless Severity set to 'serious' from 'normal' > -- Stopping processing here. Please contact me if you need assistance. -- 765419:

Bug#797651: marked as done (mummy fails to build (libgccxml-dev vs GCC-5))

Your message dated Sun, 13 Dec 2015 19:00:53 + with message-id and subject line Bug#806818: Removed package(s) from unstable has caused the Debian Bug report #797651, regarding mummy fails to build (libgccxml-dev vs GCC-5) to be marked as done. This means

Bug#807675: marked as done (dcmtkpp: FTBFS: SCU Failed: 0006:0213 Data dictionary missing)

Your message dated Sun, 13 Dec 2015 18:19:55 + with message-id and subject line Bug#807675: fixed in dcmtkpp 0.3.1-3 has caused the Debian Bug report #807675, regarding dcmtkpp: FTBFS: SCU Failed: 0006:0213 Data dictionary missing to be marked as done.

Bug#750904: marked as done (scidavis: FTBFS on arm*: fatal error: sipAPIscidavis.h: No such file or directory)

Your message dated Sun, 13 Dec 2015 19:06:38 +0100 with message-id <20151213180638.ga31...@georges.khaznadar.fr> and subject line Re: Build on arm* has caused the Debian Bug report #750904, regarding scidavis: FTBFS on arm*: fatal error: sipAPIscidavis.h: No such file or directory to be marked as

Processed: tagging 807705, tagging 728955, tagging 807737, found 807502 in 2.25+Atmel3.5.0-1, tagging 807564

Processing commands for cont...@bugs.debian.org: > tags 807705 + sid stretch Bug #807705 [src:xserver-xorg-video-openchrome] xserver-xorg-video-openchrome: FTBFS: /usr/include/xorg/os.h:558:1: error: expected identifier or '(' before '__extension__' Added tag(s) stretch and sid. > tags 728955 +

Bug#804541: marked as done (lvm2 Build-depends on obsolete package libcorosync-dev)

Your message dated Sun, 13 Dec 2015 18:30:38 + with message-id and subject line Bug#804541: fixed in lvm2 2.02.133-2 has caused the Debian Bug report #804541, regarding lvm2 Build-depends on obsolete package libcorosync-dev to be marked as done. This

Processed: affects 799322, found 775385 in 1.16.6-1, found 771085 in 3.18.2-1

Processing commands for cont...@bugs.debian.org: > affects 799322 + libpocl-dbg Bug #799322 [src:pocl] pocl: FTBFS: (gcc5 related?) symbols mismatches + test failures Added indication that 799322 affects libpocl-dbg > found 775385 1.16.6-1 Bug #775385 [lightdm] lightdm: unowned symlink after

Processed: severity of 807800 is important

Processing commands for cont...@bugs.debian.org: > severity 807800 important Bug #807800 [heimdall-flash] heimdall-flash: heimdall fails on files larger than 2GB Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 807800:

Bug#804590: redhat-cluster: build-depends on libcorosync-dev which is no longer built

On Mon, 09 Nov 2015 20:39:32 +0100, Emilio Pozuelo Monfort wrote: > Your package build-depends on libcorosync-dev which is no longer > built by corosync. Please switch to the appropriate packages to > build against the new version. Afer replacing libcorosync-dev with libcorosync-common-dev and

Bug#800216: marked as done (gniall: Please migrate a supported debhelper compat level)

Your message dated Sun, 13 Dec 2015 21:17:35 -0200 with message-id and subject line gniall: diff for NMU version 0.7.1-7.1 has caused the Debian Bug report #800216, regarding gniall: Please migrate a supported debhelper compat

Bug#793187: marked as done (arb: FTBFS with gcc 4.9.2+)

Your message dated Sun, 13 Dec 2015 23:17:08 + with message-id and subject line Bug#793187: fixed in arb 6.0.2-1+deb8u1 has caused the Debian Bug report #793187, regarding arb: FTBFS with gcc 4.9.2+ to be marked as done. This means that you claim that the

Processed: Re: Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

Processing control commands: > reassign -1 gcc-5.0 Bug #807756 [libtasn1-6] gnubg: fails to start. hangs using 100% of one cpu core Bug reassigned from package 'libtasn1-6' to 'gcc-5.0'. Warning: Unknown package 'gcc-5.0' Warning: Unknown package 'gcc-5.0' Ignoring request to alter found versions

Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core

Control: reassign -1 gcc-5.0 Control: severity -1 important Andreas Metzler writes: > Some more points of strangeness: > jessie's gnubg package (1.04.000-1) works on current stretch. > Rebuilding the jessie source on current sid produces a binary which > fails. > Rebuilding

Bug#807878: gnome: Gnome freezes when root windows are open on user screen.

Package: gnome Version: 1:3.14+3 Severity: critical Justification: causes serious data loss *** Scenario *** Non-classic gnome logged as a regular user and some root windows open. e.g. synaptic, nautilus-as-root, root-terminal, etc. *** Causing the problem *** Hitting the upper left

Bug#801597: marked as done (PIE and stack protection appear missing since update to GCC-5)

Your message dated Sun, 13 Dec 2015 22:13:17 + with message-id and subject line Bug#801597: fixed in hardening-wrapper 2.8+nmu1 has caused the Debian Bug report #801597, regarding PIE and stack protection appear missing since update to GCC-5 to be marked

Processed: severity of 799275 is important

Processing commands for cont...@bugs.debian.org: > severity 799275 important Bug #799275 [src:gtk+2.0] [GDK] patch - avoid integer overflow when allocating a large block of memory Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need

Bug#802579: marked as done (binutils changed ld.bfd / ld.gold files and symlinks)

Your message dated Sun, 13 Dec 2015 22:13:17 + with message-id and subject line Bug#802579: fixed in hardening-wrapper 2.8+nmu1 has caused the Debian Bug report #802579, regarding binutils changed ld.bfd / ld.gold files and symlinks to be marked as done.

Bug#786836: marked as done (packaging not yet ready for mass/stable usage)

Your message dated Sun, 13 Dec 2015 23:02:47 + with message-id and subject line Bug#786836: fixed in rustc 1.5.0+dfsg1-1 has caused the Debian Bug report #786836, regarding packaging not yet ready for mass/stable usage to be marked as done. This means

Bug#804590: [Debian-ha-maintainers] Bug#804590: redhat-cluster: build-depends on libcorosync-dev which is no longer built

gregor herrmann writes: > On Mon, 09 Nov 2015 20:39:32 +0100, Emilio Pozuelo Monfort wrote: > >> Your package build-depends on libcorosync-dev which is no longer >> built by corosync. Please switch to the appropriate packages to >> build against the new version. > > Afer

Processed: reassign 807014 to ros-message-runtime, fixed 807014 in 0.4.12-3

Processing commands for cont...@bugs.debian.org: > reassign 807014 ros-message-runtime 0.4.12-2 Bug #807014 {Done: Jochen Sprickerhof } [message-runtime,ros-message-runtime] ros-message-runtime and message-runtime: error when trying to install together Warning:

Bug#807547: marked as done ([alfred] copyright file incomplete)

Your message dated Mon, 14 Dec 2015 01:48:51 + with message-id and subject line Bug#807547: fixed in alfred 2015.2-1 has caused the Debian Bug report #807547, regarding [alfred] copyright file incomplete to be marked as done. This means that you claim

Bug#807546: marked as done ([alfred] Fails to build on non-linux systems)

Your message dated Mon, 14 Dec 2015 01:48:51 + with message-id and subject line Bug#807546: fixed in alfred 2015.2-1 has caused the Debian Bug report #807546, regarding [alfred] Fails to build on non-linux systems to be marked as done. This means that you

Processed: tagging 807735, tagging 807660, tagging 807659, found 807666 in 3.1-6, tagging 807706, tagging 807657

Processing commands for cont...@bugs.debian.org: > tags 807735 + sid stretch Bug #807735 [src:gmpc-plugins] gmpc-plugins: FTBFS: libmpd-internal.h:210:10: error: expected identifier or '(' before '__extension__' Ignoring request to alter tags of bug #807735 to the same tags previously set > tags

Bug#807730: marked as done (incorrect bsd/unistd.h header)

Your message dated Mon, 14 Dec 2015 04:41:20 + with message-id and subject line Bug#807730: fixed in libbsd 0.8.1-1 has caused the Debian Bug report #807730, regarding incorrect bsd/unistd.h header to be marked as done. This means that you claim that the

Bug#807885: libstdc++6-6-dbg: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/debug/libstdc++.a

Package: libstdc++6-6-dbg Version: 6-20151211-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because

Bug#806840: marked as done (libbsd: FTBFS on non-Linux systems)

Your message dated Mon, 14 Dec 2015 04:41:20 + with message-id and subject line Bug#806840: fixed in libbsd 0.8.1-1 has caused the Debian Bug report #806840, regarding libbsd: FTBFS on non-Linux systems to be marked as done. This means that you claim that

Processed: severity of 803782 is normal, severity of 805817 is serious

Processing commands for cont...@bugs.debian.org: > severity 803782 normal Bug #803782 [ftp.debian.org] RM: drawtk - unmaintained, no rev deps, depends on gstreamer 0.10 Severity set to 'normal' from 'serious' > severity 805817 serious Bug #805817 [ftp.debian.org] RM: instanbul - dead upstream,

Bug#807784: [Pkg-octave-devel] Bug#807784: octave-optim suggests `lyx`

Great! Thanks! So lyx was supposed to be used for "reading" some documentation? Well, I would not think that lyx can be assumed to be a tool to do so. Octave users will use `help` and `info`, and when necessary, the browser and PDF reader, but certainly not lyx. Thanks for the effort! On Sun, Dec

Processed: Re: [Pkg-octave-devel] Bug#807784: octave-optim suggests `lyx`

Processing control commands: > severity -1 normal Bug #807784 [octave-optim] octave-optim suggests `lyx` Severity set to 'normal' from 'serious' -- 807784: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#807784: [Pkg-octave-devel] Bug#807784: octave-optim suggests `lyx`

Control: severity -1 normal * Hormet Yiltiz [2015-12-12 19:29]: Package: octave-optim Version: 1.4.1-1+b1 Severity: serious Justification: Policy 7.2 octave-optim suggests lyx, which is a office suite that makes working with LaTeX easy, and implements a way for

Processed: reassign 804993 to libjs-pie-doc, fixed 804993 in 1.0.0+dfsg-2, severity of 804993 is serious

Processing commands for cont...@bugs.debian.org: > reassign 804993 libjs-pie-doc 1.0.0+dfsg-1 Bug #804993 {Done: Michael Fladischer } [libvirtd] python-django-classy-tags-doc and libjs-pie-doc: error when trying to install together Warning: Unknown package 'libvirtd' Bug

Bug#806167: python-twisted fails to upgrade because of missing/incorrect replaces/breaks

Followup-For: Bug #806167 Hi, python-twisted-core should have Breaks matching the recently added Replaces, otherwise it allows for partial up- and downgrades that result in broken (but successfully installed according to dpkg) packages (because files have disappeared). Andreas

Bug#803295: marked as done (prepare for giflib5)

Your message dated Mon, 14 Dec 2015 07:35:58 + with message-id and subject line Bug#803295: fixed in spamprobe 1.4d-14 has caused the Debian Bug report #803295, regarding prepare for giflib5 to be marked as done. This means that you claim that the problem

Bug#807589: libechonest: FTBFS on all architectures due to mismatched symbols file(s)

Hi, I'm a little bit confused about the sh4 build of libechonest. It failed because there appears a new symbol: (c++)"QDebug::operator<<(QByteArray const&)@Base" 2.3.1-0.3 on all architectures there is the following Symbol: (c++)"QDebug::operator<<(QString const&)@Base" 2.3.1 Why does sh4

Bug#784070: Stable is still affected

Are there any plans to produce a stable update containing this fix?