Bug#795340: pymappergui crashes due to missing dependencies (mapper, python-scipy, python-matplotlib)

Package: pymappergui Version: 0.1-1 Severity: serious Justification: 4 Dear Maintainer, pymappergui crashes just after start due to missing dependencies: Traceback (most recent call last): File "/usr/bin/pymappergui", line 25, in from pymappergui.mymapper import MyMapper File "/usr/lib/

Bug#794271: marked as done (FTBFS: "StubbingNilTest#test_should_allow_stubbing_method_on_nil" and others fail)

Your message dated Thu, 13 Aug 2015 06:49:08 + with message-id and subject line Bug#794271: fixed in ruby-mocha 1.1.0-2 has caused the Debian Bug report #794271, regarding FTBFS: "StubbingNilTest#test_should_allow_stubbing_method_on_nil" and others fail to be marked as done. This means that

Bug#788906: marked as done (ruby-aws-sdk and ruby-aws: error when trying to install together)

Your message dated Thu, 13 Aug 2015 06:34:33 + with message-id and subject line Bug#788906: fixed in ruby-aws 2.10.2-2 has caused the Debian Bug report #788906, regarding ruby-aws-sdk and ruby-aws: error when trying to install together to be marked as done. This means that you claim that the

Bug#795336: linux-image-4.0.0-2-amd64: kernel causes mounted usb drives to timeout transfers

Package: src:linux Version: 4.0.8-2 Severity: grave Tags: lfs Justification: renders package unusable It thought this was an encfs problem until I looked at the drive post umount. The access light was still flashing and post-disconnect I get a drive cannot be accessed error. Not only do drive tran

Bug#795233: sflphone: FTBFS: error: call of overloaded 'basic_string(int, int)' is ambiguous

tag 795233 patch user ubuntu-de...@lists.ubuntu.com usertags 795233 origin-ubuntu ubuntu-patch wily thanks Hello again, Martin Pitt [2015-08-12 7:48 +0200]: > | sipaccount.cpp: In constructor 'SIPAccount::SIPAccount(const string&, > bool)': > | sipaccount.cpp:144:66: error: call of overloaded '

Processed: severity of 793250 is serious

Processing commands for cont...@bugs.debian.org: > severity 793250 serious Bug #793250 [src:insighttoolkit4] insighttoolkit4: change of type in system_error might break with GCC-5 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistan

Bug#750918: marked as done (openmsx-catapult: Please update to use wxwidgets3.0)

Your message dated Thu, 13 Aug 2015 03:36:57 + with message-id and subject line Bug#750918: fixed in openmsx-catapult 0.11.0-2 has caused the Debian Bug report #750918, regarding openmsx-catapult: Please update to use wxwidgets3.0 to be marked as done. This means that you claim that the probl

Processed: tagging 795297, tagging 795259, tagging 795238, tagging 795237

Processing commands for cont...@bugs.debian.org: > tags 795297 + sid Bug #795297 [powertop] powertop: not installable as broken by libstdc++6 Added tag(s) sid. > tags 795259 + sid stretch Bug #795259 [python-shapely] python-shapely: Drop hardcoded libgeos-c1 dependencies Added tag(s) stretch and

Bug#780865: Fix also needed for i386 (and squeeze-backports)

On Wed, 12 Aug 2015, siev...@math2.nat.tu-bs.de wrote: > Hello, > > it seems that openafs 1.6.1-3+deb7u4 which fixes (not only) > bug #780865 is available in wheezy-proposed-updates only for the amd64 > architecture, while the same problem exists for 32 bit systems. That's just how Debian works -

Bug#791283: marked as done (siscone: library transition may be needed when GCC 5 is the default)

Your message dated Thu, 13 Aug 2015 00:55:11 + with message-id <8aabe0e7605b0891d89634083edd8...@dogguy.org> and subject line Re: Bug#791283: siscone: library transition may be needed when GCC 5 is the default has caused the Debian Bug report #791283, regarding siscone: library transition may

Processed: Re: Bug#791283: siscone: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791283 [src:siscone] siscone: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791283 [src:siscone] siscone: library transition may be needed when GCC 5 is the default Severity se

Processed: Re: Bug#791283: siscone: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791283 [src:siscone] siscone: library transition may be needed when GCC 5 is the default Ignoring request to alter tags of bug #791283 to the same tags previously set > severity -1 serious Bug #791283 [src:siscone] siscone: library transitio

Bug#791283: siscone: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:14:17PM +, Matthias Klose wrote: > - Decide if the symbols matching __cxx11 or B5cxx11 are part of the >library API, and are used by the reverse dependencies of the >library. > This library uses s

Bug#791276: shiboken: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:14:09PM +, Matthias Klose wrote: > - Decide if the symbols matching __cxx11 or B5cxx11 are part of the >library API, and are used by the reverse dependencies of the >library. > Exposes a use of st

Processed: Re: Bug#791276: shiboken: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791276 [src:shiboken] shiboken: library transition may be needed when GCC 5 is the default Ignoring request to alter tags of bug #791276 to the same tags previously set > severity -1 serious Bug #791276 [src:shiboken] shiboken: library trans

Processed: Re: Bug#791276: shiboken: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791276 [src:shiboken] shiboken: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791276 [src:shiboken] shiboken: library transition may be needed when GCC 5 is the default Severit

Processed: Re: Bug#791273: scalc: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791273 [src:scalc] scalc: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791273 [src:scalc] scalc: library transition may be needed when GCC 5 is the default Severity set to 'se

Bug#791273: scalc: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:14:06PM +, Matthias Klose wrote: > - Decide if the symbols matching __cxx11 or B5cxx11 are part of the >library API, and are used by the reverse dependencies of the >library. > Exposes std::string

Processed: Re: Bug#791273: scalc: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791273 [src:scalc] scalc: library transition may be needed when GCC 5 is the default Ignoring request to alter tags of bug #791273 to the same tags previously set > severity -1 serious Bug #791273 [src:scalc] scalc: library transition may be

Processed: Re: Bug#791055: gnome-chemistry-utils: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791055 [src:gnome-chemistry-utils] gnome-chemistry-utils: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791055 [src:gnome-chemistry-utils] gnome-chemistry-utils: library transi

Bug#791055: gnome-chemistry-utils: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:10:14PM +, Matthias Klose wrote: > - Decide if the symbols matching __cxx11 or B5cxx11 are part of the >library API, and are used by the reverse dependencies of the >library. > libgcu0 has no reve

Processed: Re: Bug#791055: gnome-chemistry-utils: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791055 [src:gnome-chemistry-utils] gnome-chemistry-utils: library transition may be needed when GCC 5 is the default Ignoring request to alter tags of bug #791055 to the same tags previously set > severity -1 serious Bug #791055 [src:gnome-c

Processed: tagging 791095

Processing commands for cont...@bugs.debian.org: > tags 791095 + confirmed Bug #791095 [src:libbpp-phyl-omics] libbpp-phyl-omics: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 79

Processed: tagging 791100

Processing commands for cont...@bugs.debian.org: > tags 791100 + confirmed Bug #791100 [src:libbpp-seq-omics] libbpp-seq-omics: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 7911

Processed: tagging 791098

Processing commands for cont...@bugs.debian.org: > tags 791098 + confirmed Bug #791098 [src:libbpp-raa] libbpp-raa: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 791098: http://b

Processed: tagging 791096

Processing commands for cont...@bugs.debian.org: > tags 791096 + confirmed Bug #791096 [src:libbpp-popgen] libbpp-popgen: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 791096: ht

Processed: tagging 791094

Processing commands for cont...@bugs.debian.org: > tags 791094 + confirmed Bug #791094 [src:libbpp-phyl] libbpp-phyl: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 791094: http:/

Processed: severity of 791094 is serious

Processing commands for cont...@bugs.debian.org: > severity 791094 serious Bug #791094 [src:libbpp-phyl] libbpp-phyl: library transition may be needed when GCC 5 is the default Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance.

Processed: severity of 791098 is serious

Processing commands for cont...@bugs.debian.org: > severity 791098 serious Bug #791098 [src:libbpp-raa] libbpp-raa: library transition may be needed when GCC 5 is the default Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -

Processed: severity of 791100 is serious

Processing commands for cont...@bugs.debian.org: > severity 791100 serious Bug #791100 [src:libbpp-seq-omics] libbpp-seq-omics: library transition may be needed when GCC 5 is the default Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need a

Processed: severity of 791095 is serious

Processing commands for cont...@bugs.debian.org: > severity 791095 serious Bug #791095 [src:libbpp-phyl-omics] libbpp-phyl-omics: library transition may be needed when GCC 5 is the default Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need

Processed: severity of 791096 is serious

Processing commands for cont...@bugs.debian.org: > severity 791096 serious Bug #791096 [src:libbpp-popgen] libbpp-popgen: library transition may be needed when GCC 5 is the default Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assista

Bug#794849: closed by Ben Hutchings (Re: Bug#794849: linux: custom linux-image packages fail to install)

On Thu, Aug 13, 2015 at 12:23 AM, Ben Hutchings wrote: > Control: reopen -1 > Control: reassign -1 os-prober > > On Wed, 2015-08-12 at 23:19 +0200, Stefan Bucur wrote: > > After some digging, I realized that the root failure seems to first > > occur inside the running kernel (!!), during the dpkg

Bug#795329: nlpsolver: FTBFS: error: package com.sun.star.uno does not exist

Source: nlpsolver Version: 0.9~beta1-10 Severity: serious Justification: fails to build from source Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: -do-compile:

Bug#795328: netcf: FTBFS: error: 'IFF_UP' undeclared (first use in this function)

Source: netcf Version: 1:0.2.3-4.1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: dutil_linux.c:

Bug#795327: knemo: FTBFS: error: 'IFF_POINTOPOINT' was not declared in this scope

Source: knemo Version: 0.7.6-2 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: /knemo-0.7.6/src/k

Processed: Re: Bug#791264: qwtplot3d: library transition may be needed when GCC 5 is the default

Processing control commands: > severity -1 serious Bug #791264 [src:qwtplot3d] qwtplot3d: library transition may be needed when GCC 5 is the default Severity set to 'serious' from 'important' > tag -1 confirmed Bug #791264 [src:qwtplot3d] qwtplot3d: library transition may be needed when GCC 5 is

Bug#795325: jruby-openssl: FTBFS: -Dmaven.multiModuleProjectDirectory system propery is not set.

Source: jruby-openssl Version: 0.9.7-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: mh_patchpo

Bug#795324: gtml: FTBFS: make[2]: gtml: Command not found

Source: gtml Version: 3.5.4-15 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: debian/rules ov

Bug#794849: closed by Ben Hutchings (Re: Bug#794849: linux: custom linux-image packages fail to install)

Control: reopen -1 Control: reassign -1 os-prober On Wed, 2015-08-12 at 23:19 +0200, Stefan Bucur wrote: > Thanks Ben for the advice and sorry for the latency. The steps you're > suggesting are indeed more straightforward. However, the generated > .deb packages still fail to install properly. I

Processed: Re: Bug#794849: closed by Ben Hutchings (Re: Bug#794849: linux: custom linux-image packages fail to install)

Processing control commands: > reopen -1 Bug #794849 {Done: Ben Hutchings } [src:linux] linux: custom linux-image packages fail to install Bug reopened Ignoring request to alter fixed versions of bug #794849 to the same values previously set > reassign -1 os-prober Bug #794849 [src:linux] linux:

Bug#795323: fpc: FTBFS: Target "linux", package "fpgtk" not found

Source: fpc Version: 2.6.4+dfsg-7 Severity: serious Justification: fails to build from source Tags: sid User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ... fpcsrc/utils/fpcm/

Bug#795322: cryptmount: FTBFS: assumes automake-1.14

Source: cryptmount Version: 5.1-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: ... Preparing t

Bug#794849: closed by Ben Hutchings (Re: Bug#794849: linux: custom linux-image packages fail to install)

On Wed, Aug 12, 2015 at 11:19 PM, Stefan Bucur wrote: > Thanks Ben for the advice and sorry for the latency. The steps you're > suggesting are indeed more straightforward. However, the generated .deb > packages still fail to install properly. I repeated the procedure on > several fresh Debian 8.1

Bug#794313: marked as done (dahdi: DAHDI-modules build fails)

Your message dated Wed, 12 Aug 2015 21:34:42 + with message-id and subject line Bug#794313: fixed in dahdi-linux 1:2.10.2~dfsg-1 has caused the Debian Bug report #794313, regarding dahdi: DAHDI-modules build fails to be marked as done. This means that you claim that the problem has been dealt

Bug#795069: marked as done (freecad: FTBFS: Parse error at "BOOST_JOIN")

Your message dated Wed, 12 Aug 2015 21:35:30 + with message-id and subject line Bug#795069: fixed in freecad 0.14.3702+dfsg-4 has caused the Debian Bug report #795069, regarding freecad: FTBFS: Parse error at "BOOST_JOIN" to be marked as done. This means that you claim that the problem has be

Bug#794849: closed by Ben Hutchings (Re: Bug#794849: linux: custom linux-image packages fail to install)

Thanks Ben for the advice and sorry for the latency. The steps you're suggesting are indeed more straightforward. However, the generated .deb packages still fail to install properly. I repeated the procedure on several fresh Debian 8.1 installations, using default settings in the installer, with th

Processed: downgrade severity

Processing commands for cont...@bugs.debian.org: > severity 792649 important Bug #792649 [src:google-glog] the demangler is not aware of the __cxx11 symbols in GCC 5's libstdc++ Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need a

Processed: Re: Bug#791250: pugixml: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791250 [src:pugixml] pugixml: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791250 [src:pugixml] pugixml: library transition may be needed when GCC 5 is the default Severity se

Bug#791267: Roland, could you check out remaining build error?

Hi Roland, or whoever might like to care. I applied the suggested patch in Git but there is some remaining Build issue (I added a snippet as TODO in d/changelog). Feel free to ping me if you are not able to deal with this in a short time frame. Kind regards Andreas. -- http://fam-tille

Bug#792649: the demangler is not aware of the __cxx11 symbols in GCC 5's libstdc++

Control: tags -1 + important ignoring the check for now. looks like the package is good enough to be used even with the test failing.

Processed (with 1 errors): Re: the demangler is not aware of the __cxx11 symbols in GCC 5's libstdc++

Processing control commands: > tags -1 + important Unknown tag/s: important. Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch

Bug#786565: [Pkg-mozext-maintainers] Bug#786565: iceweasel: breaks xul-ext-requestpolicy

Hi, Le 12/08/2015 20:23, Riku Saikkonen a écrit : > I guess the exception iceweasel has for stable security updates by > upgrading to a new major release should also make it possible to update > extensions in stable when there are compatibility problems like this > one? This process already star

Bug#795102: libgraphicsmagick1-dev: undefined reference to `Magick::Color::Color(unsigned short, unsigned short, unsigned short)'

A quick grep through the sources of rev-deps shows that these packages use the PixelPacket structure: gnudatalanguage octave pdf2djvu python-pgmagick witty xastir I expect them all to be affected by this ABI breakage. So please don't paper over the problem with Breaks, but either revert the Q

Bug#791235: pajeng: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:13:25PM +, Matthias Klose wrote: > - Rebuild the library using g++/g++-5 from experimental. Note that >most likely all C++ libraries within the build dependencies need >a rebuild too. You can find t

Processed: Re: Bug#791235: pajeng: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791235 [src:pajeng] pajeng: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791235 [src:pajeng] pajeng: library transition may be needed when GCC 5 is the default Severity set to

Processed: Re: Bug#791235: pajeng: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791235 [src:pajeng] pajeng: library transition may be needed when GCC 5 is the default Ignoring request to alter tags of bug #791235 to the same tags previously set > severity -1 serious Bug #791235 [src:pajeng] pajeng: library transition ma

Bug#750918: Fixed in last upload

On Wed, Aug 12, 2015 at 07:17:03PM +, Bas Wijnen wrote: > I'll make sure I do that now. I think a binNMU would fix this bug, right? It'll need a sourceful upload as debian/control needs changing back to say libwxgtk3.0-dev rather than libwxgtk2.8-dev: https://sources.debian.net/src/openmsx-c

Bug#750918: Fixed in last upload

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Aug 11, 2015 at 06:24:42AM +0100, Olly Betts wrote: > The wx BD has reverted to libwxgtk2.8-dev in 0.11.0-1: How did that happen? I thought I removed every trace of the old library from my system... I'll make sure I do that now. I think a b

Bug#795300: FTBFS on most architectures

Package: openscad Version: 2015.03-1+dfsg-1 Severity: serious Due to the introduction of strict regression tests, OpenSCAD now fails to build on most architectures (see [1]) at different stages of the unit tests. The currently planned course of action is to * check what made it fail on i386, fi

Bug#795102: marked as done (libgraphicsmagick1-dev: undefined reference to `Magick::Color::Color(unsigned short, unsigned short, unsigned short)')

Your message dated Wed, 12 Aug 2015 19:04:22 + with message-id and subject line Bug#795102: fixed in graphicsmagick 1.3.21-3 has caused the Debian Bug report #795102, regarding libgraphicsmagick1-dev: undefined reference to `Magick::Color::Color(unsigned short, unsigned short, unsigned short)

Processed: Re: Bug#791232: openvrml: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791232 [src:openvrml] openvrml: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791232 [src:openvrml] openvrml: library transition may be needed when GCC 5 is the default Severit

Bug#791232: openvrml: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:13:22PM +, Matthias Klose wrote: > - Decide if the symbols matching __cxx11 or B5cxx11 are part of the >library API, and are used by the reverse dependencies of the >library. > There are some std:

Processed: Re: Bug#791232: openvrml: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791232 [src:openvrml] openvrml: library transition may be needed when GCC 5 is the default Ignoring request to alter tags of bug #791232 to the same tags previously set > severity -1 serious Bug #791232 [src:openvrml] openvrml: library trans

Processed: Re: Bug#792655: Further details on 792655

Processing control commands: > tags -1 +unreproducible Bug #792655 [cups-daemon] cups-daemon: cupsd sefaults when handling ssl with libgnutls Added tag(s) unreproducible. -- 792655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792655 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#792655: Further details on 792655

Control: tags -1 +unreproducible Hi Johannes, and thanks for your bugreport. Sorry for the time it took me to answer this serious bug. Le vendredi, 17 juillet 2015, 10.11:05 Johannes Dröge a écrit : > I cleared configuration files and reinstalled all packages. The daemon > is reproducibly crashi

Bug#793319: FTBFS: ImportError: cannot import name component_re

On Wed, Aug 12, 2015 at 04:31:15PM +0300, Gediminas Paulauskas wrote: > Now that Bug#779324 is fixed, a simple rebuild would fix the problem. Looks good, yep.

Bug#786565: iceweasel: breaks xul-ext-requestpolicy

Hi, Just a heads-up on this bug: with the recent security update to iceweasel, this bug now affects Debian stable. Thus the package xul-ext-requestpolicy is now completely unusable in the current Debian stable release. So should this bug now be reopened as release-critical, or a separate bug crea

Bug#794489: Re: Bug#795219: nmu: gimagereader_3.1-1

Using apt-rdepends -r libtesseract3, I think the affected packages are gimagereader and libsikuli-script-jni.

Bug#794489: Re: Bug#795219: nmu: gimagereader_3.1-1

>could you please comment on Juliens mail? Do you plan to >do the proposed changes? Depends how many packages are affected. Transitions are a bunch of work, and I think we are also in some special situation due to the GCC transition. So if it is just one binMNU then I think that might be the way t

Bug#795297: powertop: not installable as broken by libstdc++6

Package: powertop Version: 2.6.1-1 Severity: grave Justification: renders package unusable powertop is blocking upgrades (or becomes uninstallable after an upgrade) because libstdc++6 breaks powertop (<= 2.6.1-1). libstdc++6 has been available in unstable for more than 10 days. powertop should be

Processed: Pending

Processing commands for cont...@bugs.debian.org: > tags 791200 +pending Bug #791200 [src:med-fichier] med-fichier: library transition may be needed when GCC 5 is the default Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 791200: http://bugs

Bug#795238: subsurface: Please remove

Le 12/08/2015 19:37, Christoph Anton Mitterer a écrit : > On Wed, 2015-08-12 at 09:31 +0200, Salvo Tomaselli wrote: >> upstream forked quite a lot of libraries. > Which? libgit, libmarble & libdivecomputer >> Packaging subsurface is >> impossible. > Other projects would do this as well and packagi

Processed: severity of 795187 is important

Processing commands for cont...@bugs.debian.org: > # this ain't serious by any means. It's important yes > # and the "broken" component is pdebuild not pbuilder itself. > severity 795187 important Bug #795187 [pbuilder] git-buildpackage: git-pbuilder does not install Build-Depends (anymore?) Bug

Bug#795238: subsurface: Please remove

On Wed, 2015-08-12 at 09:31 +0200, Salvo Tomaselli wrote: > upstream forked quite a lot of libraries. Which? > Packaging subsurface is > impossible. Other projects would do this as well and packaging them works nevertheless... and subsurface is already packaged, so it's definitely not impossible.

Processed: Re: Bug#791230: openrpt: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791230 [src:openrpt] openrpt: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791230 [src:openrpt] openrpt: library transition may be needed when GCC 5 is the default Severity se

Processed: Re: Bug#791230: openrpt: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791230 [src:openrpt] openrpt: library transition may be needed when GCC 5 is the default Ignoring request to alter tags of bug #791230 to the same tags previously set > severity -1 serious Bug #791230 [src:openrpt] openrpt: library transitio

Bug#791230: openrpt: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:13:20PM +, Matthias Klose wrote: > - Decide if the symbols matching __cxx11 or B5cxx11 are part of the >library API, and are used by the reverse dependencies of the >library. > It even has std::li

Bug#791251: (no subject)

Hi, I have a 0.4.3-1 in the git repository already. The gcc 5 transition is a rebuild away, since there are no rdeps. Thanks, Snark on #debian-science

Bug#780865: Fix also needed for i386 (and squeeze-backports)

Hello, it seems that openafs 1.6.1-3+deb7u4 which fixes (not only) bug #780865 is available in wheezy-proposed-updates only for the amd64 architecture, while the same problem exists for 32 bit systems. And what about squeeze, which has a 3.2 kernel and openafs 1.6.1-3+deb7u2~bpo60+1 in backports?

Bug#795287: evolution-data-server: Cannot connect to gmail account any longer

Package: evolution-data-server Version: 3.16.3-1.1 Severity: serious Tags: sid stretch Hi, With the latest debian packages, 3.16.3-1.1 evo cannot any longer connect to Contacts and the gmail account: Failed to connect to 'Contacts' Cannot find a corresponding account in the org.gnome.OnlineAccou

Bug#794160: marked as done (FTBFS: The semantics of `RSpec::Core::Pending#pending` have changed in RSpec 3.)

Your message dated Wed, 12 Aug 2015 16:02:25 + with message-id and subject line Bug#794160: fixed in ruby-beautify 0.97.3-1 has caused the Debian Bug report #794160, regarding FTBFS: The semantics of `RSpec::Core::Pending#pending` have changed in RSpec 3. to be marked as done. This means tha

Bug#795048: marked as done (ruby-roxml: FTBFS: rspec3 port(?): ...name_explicit?.should be_true)

Your message dated Wed, 12 Aug 2015 16:02:53 + with message-id and subject line Bug#795048: fixed in ruby-roxml 3.3.1-4 has caused the Debian Bug report #795048, regarding ruby-roxml: FTBFS: rspec3 port(?): ...name_explicit?.should be_true to be marked as done. This means that you claim that

Bug#794274: marked as done (FTBFS: tests fail: undefined method `stub!' for #)

Your message dated Wed, 12 Aug 2015 16:02:45 + with message-id and subject line Bug#794274: fixed in ruby-omniauth-github 1.1.2-2 has caused the Debian Bug report #794274, regarding FTBFS: tests fail: undefined method `stub!' for # to be marked as done. This means that you claim that the pro

Bug#724140: marked as done (op-panel: FTBFS: POD errors)

Your message dated Wed, 12 Aug 2015 15:59:03 + with message-id and subject line Bug#795252: Removed package(s) from unstable has caused the Debian Bug report #724140, regarding op-panel: FTBFS: POD errors to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#732725: marked as done (libogre-perl: Please upgrade OGRE dependency to 1.9 when upstream ready)

Your message dated Wed, 12 Aug 2015 15:54:29 + with message-id and subject line Bug#795067: Removed package(s) from unstable has caused the Debian Bug report #732725, regarding libogre-perl: Please upgrade OGRE dependency to 1.9 when upstream ready to be marked as done. This means that you c

Bug#795242: marked as done (incomplete copyright information)

Your message dated Wed, 12 Aug 2015 15:50:22 + with message-id and subject line Bug#795242: fixed in coin3 3.1.4~abc9f50+dfsg1-1 has caused the Debian Bug report #795242, regarding incomplete copyright information to be marked as done. This means that you claim that the problem has been dealt

Bug#747831: marked as done (libreoffice-accessodf: can't be installed with current libreoffice)

Your message dated Wed, 12 Aug 2015 15:51:53 + with message-id and subject line Bug#794934: Removed package(s) from unstable has caused the Debian Bug report #747831, regarding libreoffice-accessodf: can't be installed with current libreoffice to be marked as done. This means that you claim t

Bug#747807: marked as done (accessodf: FTBFS: error: method createMessageBox in interface XMessageBoxFactory cannot be applied to given types)

Your message dated Wed, 12 Aug 2015 15:51:53 + with message-id and subject line Bug#794934: Removed package(s) from unstable has caused the Debian Bug report #743634, regarding accessodf: FTBFS: error: method createMessageBox in interface XMessageBoxFactory cannot be applied to given types to

Bug#795241: marked as done (source package contains *.exe without source)

Your message dated Wed, 12 Aug 2015 15:50:22 + with message-id and subject line Bug#795241: fixed in coin3 3.1.4~abc9f50+dfsg1-1 has caused the Debian Bug report #795241, regarding source package contains *.exe without source to be marked as done. This means that you claim that the problem ha

Bug#743634: marked as done (libreoffice-accessodf: MessageBox API changed in LO 4.2 :/)

Your message dated Wed, 12 Aug 2015 15:51:53 + with message-id and subject line Bug#794934: Removed package(s) from unstable has caused the Debian Bug report #743634, regarding libreoffice-accessodf: MessageBox API changed in LO 4.2 :/ to be marked as done. This means that you claim that the

Bug#791315: xylib: library transition may be needed when GCC 5 is the default

user release.debian@packages.debian.org usertag 791315 + transition block 791315 by 790756 reassign 791315 release.debian.org retitle 791315 transition: xylib (GCC 5) severity 791315 normal thanks On 2015-08-10 14:53:35, Julien Cristau wrote: > Control: severity -1 serious > Control: tag -1 co

Processed: Re: Bug#791315: xylib: library transition may be needed when GCC 5 is the default

Processing commands for cont...@bugs.debian.org: > user release.debian@packages.debian.org Setting user to release.debian@packages.debian.org (was sramac...@debian.org). > usertag 791315 + transition There were no usertags set. Usertags are now: transition. > block 791315 by 790756 Bug #7

Bug#788708: iceweasel: GStreamer causes segmentation fault

can't reproduce using 38.2.0esr-1~deb7u1

Bug#791228: openlayer: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:13:18PM +, Matthias Klose wrote: > - Rebuild the library using g++/g++-5 from experimental. Note that >most likely all C++ libraries within the build dependencies need >a rebuild too. You can find t

Processed: Re: Bug#791228: openlayer: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791228 [src:openlayer] openlayer: library transition may be needed when GCC 5 is the default Added tag(s) confirmed. > severity -1 serious Bug #791228 [src:openlayer] openlayer: library transition may be needed when GCC 5 is the default Sev

Processed: Re: Bug#791228: openlayer: library transition may be needed when GCC 5 is the default

Processing control commands: > tags -1 + confirmed Bug #791228 [src:openlayer] openlayer: library transition may be needed when GCC 5 is the default Ignoring request to alter tags of bug #791228 to the same tags previously set > severity -1 serious Bug #791228 [src:openlayer] openlayer: library t

Bug#791251: pynac: diff for NMU version 0.3.7-1.1

Control: tags 791251 + patch Control: tags 791251 + pending Dear maintainer, I've prepared an NMU for pynac (versioned as 0.3.7-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru pynac-0.3.7/debian/changelog pynac-0

Processed: pynac: diff for NMU version 0.3.7-1.1

Processing control commands: > tags 791251 + patch Bug #791251 [src:pynac] pynac: library transition may be needed when GCC 5 is the default Added tag(s) patch. > tags 791251 + pending Bug #791251 [src:pynac] pynac: library transition may be needed when GCC 5 is the default Added tag(s) pending.

Bug#791330: usbprog: library transition may be needed when GCC 5 is the default

Control: tags -1 + confirmed Control: severity -1 serious On Fri, Jul 03, 2015 at 01:14:46PM +, Matthias Klose wrote: > - Rebuild the library using g++/g++-5 from experimental. Note that >most likely all C++ libraries within the build dependencies need >a rebuild too. You can find t

  1   2   >