Bug#739286: marked as done (Buiuld-depends on radiusclient-ng, scheduled to be removed)

Your message dated Wed, 26 Feb 2014 07:49:06 + with message-id and subject line Bug#739286: fixed in kamailio 4.1.1-4 has caused the Debian Bug report #739286, regarding Buiuld-depends on radiusclient-ng, scheduled to be removed to be marked as done. This means that you claim that the problem

Bug#721621: [Pkg-nagios-devel] Bug#721621: dependency change s/libradiusclient-ng2/libfreeradius-client2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Daniel, Am 02.02.14 22:18, schrieb Daniel Pocock: > Looks like argument 1 and 6 are new. They may or may not be > needed, if we are lucky you can just insert 0 for missing arguments > and it will emulate the old behavior but that is not something

Bug#740106: libraw: FTBFS on 32-bit platforms: symbols not quite as expected

Hi! When fixing the symbols files, please also have a look at the build logs for all the Debian ports which are affected as well [1]. Since the build logs all contain the necessary diffs for the symbols files, you have all the information you need to fix them. Here's a bug report which shows the

Bug#740139: gnome-maps fails to start

Package: gnome-maps Version: 3.10.2-1 Severity: grave Justification: renders package unusable Trying to start gnome-maps I get the following stderr output: JS ERROR: !!! Exception was: Gio.DBusError: Error calling StartServiceByName for org.freedesktop.GeoClue2: GDBus.Error:org.freedesktop.

Bug#733423: marked as done (ruby-activesupport-3.2 should depend on ruby-minitest or drop port-to-minitest.patch)

Your message dated Wed, 26 Feb 2014 03:23:35 + with message-id and subject line Bug#733423: fixed in rails-3.2 3.2.17-1 has caused the Debian Bug report #733423, regarding ruby-activesupport-3.2 should depend on ruby-minitest or drop port-to-minitest.patch to be marked as done. This means th

Bug#737953: marked as done (itstool: FTBFS: configure: error: no suitable Python interpreter found)

Your message dated Wed, 26 Feb 2014 03:20:42 + with message-id and subject line Bug#737953: fixed in itstool 2.0.2-2 has caused the Debian Bug report #737953, regarding itstool: FTBFS: configure: error: no suitable Python interpreter found to be marked as done. This means that you claim that

Bug#728139: marked as done (brutefir: FTBFS on kfreebsd-i386: fftw_convolver.c:(.text+0x5288): undefined reference to `convolver_sse_convolve_add')

Your message dated Wed, 26 Feb 2014 03:18:42 + with message-id and subject line Bug#728139: fixed in brutefir 1.0m-1 has caused the Debian Bug report #728139, regarding brutefir: FTBFS on kfreebsd-i386: fftw_convolver.c:(.text+0x5288): undefined reference to `convolver_sse_convolve_add' to be

Bug#734268: linux-image-3.12-1-amd64: NFS-related crashes

Control: severity -1 important Control: tag -1 upstream I recognise it's a major problem for you but I'm afraid it's not strictly a critical severity. I found a similar bug report against Fedora: . That bug report has two patches which were su

Processed: Re: Bug#734268: linux-image-3.12-1-amd64: NFS-related crashes

Processing control commands: > severity -1 important Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Severity set to 'important' from 'critical' > tag -1 upstream Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Added tag(s) upstream. -- 734268: http://

Bug#739998: marked as done (cobertura: FTBFS: Maven error)

Your message dated Wed, 26 Feb 2014 00:04:32 + with message-id and subject line Bug#74: fixed in maven-repo-helper 1.8.7 has caused the Debian Bug report #74, regarding cobertura: FTBFS: Maven error to be marked as done. This means that you claim that the problem has been dealt with.

Bug#737032: marked as done (thin: looks for vendor_ruby multiarch libs in wrong location)

Your message dated Tue, 25 Feb 2014 23:50:23 + with message-id and subject line Bug#737032: fixed in thin 1.3.1-5 has caused the Debian Bug report #737032, regarding thin: looks for vendor_ruby multiarch libs in wrong location to be marked as done. This means that you claim that the problem h

Bug#738432: marked as done (ruby-vegas: FTBFS: ERROR: Test "ruby2.0" failed: LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser)

Your message dated Tue, 25 Feb 2014 23:50:23 + with message-id and subject line Bug#737032: fixed in thin 1.3.1-5 has caused the Debian Bug report #737032, regarding ruby-vegas: FTBFS: ERROR: Test "ruby2.0" failed: LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-lin

Bug#735868: marked as done (activesupport needs minitest, but does not require it explicitly)

Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id <20140225231854.GA6632@spin> and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly to be marked as done. This means that you cl

Processed: Bug in Debian patch

Processing control commands: > tags -1 + confirmed Bug #737032 [thin] thin: looks for vendor_ruby multiarch libs in wrong location Bug #738432 [thin] ruby-vegas: FTBFS: ERROR: Test "ruby2.0" failed: LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser

Bug#735865: marked as done (activesupport needs minitest, but does not require it explicitly)

Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id <20140225231854.GA6632@spin> and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly to be marked as done. This means that you cl

Bug#735867: marked as done (activesupport needs minitest, but does not require it explicitly)

Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id <20140225231854.GA6632@spin> and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly to be marked as done. This means that you cl

Bug#735860: marked as done (activesupport needs minitest, but does not require it explicitly)

Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id <20140225231854.GA6632@spin> and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly to be marked as done. This means that you cl

Bug#735863: marked as done (activesupport needs minitest, but does not require it explicitly)

Your message dated Wed, 26 Feb 2014 00:18:54 +0100 with message-id <20140225231854.GA6632@spin> and subject line not found in 3.2.16-3+0 has caused the Debian Bug report #735865, regarding activesupport needs minitest, but does not require it explicitly to be marked as done. This means that you cl

Bug#737032: Bug in Debian patch

Control: tags -1 + confirmed This is likely a bug in fix_require_path_for_thin_parser.patch. Haven't looked closely if this can be fixed in a better way (i.e. without hardcoding locations, even though in 2.0 hardcoding would be less bad). -- ,''`. Christian Hofstaedtler : :' : Debian Develop

Processed: fixed 735868 in 3.2.16-3+0

Processing commands for cont...@bugs.debian.org: > fixed 735868 3.2.16-3+0 Bug #735868 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735860 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735863 [ruby

Processed: notfound 735868 in 3.2.16-3+0

Processing commands for cont...@bugs.debian.org: > notfound 735868 3.2.16-3+0 Bug #735868 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735860 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735863 [r

Processed: found 735868 in 3.2.16-1

Processing commands for cont...@bugs.debian.org: > found 735868 3.2.16-1 Bug #735868 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735860 [ruby-activesupport-3.2] activesupport needs minitest, but does not require it explicitly Bug #735863 [ruby-a

Bug#686181: marked as done (Please allow translation of all debconf templates)

Your message dated Tue, 25 Feb 2014 23:03:19 + with message-id and subject line Bug#686181: fixed in icecast2 2.3.3-2 has caused the Debian Bug report #686181, regarding Please allow translation of all debconf templates to be marked as done. This means that you claim that the problem has been

Bug#740119: nemo: FTBFS with new gtk+ because of GTK_DISABLE_DEPRECATED

Source: nemo Version: 1.8.4-1 Severity: serious Your package FTBFS on sid since the gtk+3.0 update. That is because you're building with -DGTK_DISABLE_DEPRECATED (plus a few others). That is a bad idea to do in Debian (it is fine if upstream does it during development) because it can cause build f

Processed: retitle 735868 to activesupport needs minitest, but does not require it explicitly ...

Processing commands for cont...@bugs.debian.org: > retitle 735868 activesupport needs minitest, but does not require it > explicitly Bug #735868 [ruby-activesupport-3.2] ruby-roxml: FTBFS: ERROR: Test "ruby1.9.1" failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot loa

Processed: reassign 735865 to ruby-activesupport-3.2, reassign 735867 to ruby-activesupport-3.2 ...

Processing commands for cont...@bugs.debian.org: > reassign 735865 ruby-activesupport-3.2 Bug #735865 [src:ruby-rabl-rails] ruby-rabl-rails: FTBFS: ERROR: Test "ruby1.9.1" failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) Bug re

Processed: merging 735865 735867 735868 735863 735860

Processing commands for cont...@bugs.debian.org: > merge 735865 735867 735868 735863 735860 Bug #735865 [ruby-activesupport-3.2] ruby-rabl-rails: FTBFS: ERROR: Test "ruby1.9.1" failed: /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': cannot load such file -- minitest (LoadError) B

Processed: severity of 721721 is serious

Processing commands for cont...@bugs.debian.org: > severity 721721 serious Bug #721721 [libpostgis-java] libpostgis-java: Installs incorrect symlink Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 721721: http://bugs.debian.

Bug#740086: marked as done (python3-crypto: Ships files which are also present in python3-crypto-dbg)

Your message dated Tue, 25 Feb 2014 22:33:38 + with message-id and subject line Bug#740086: fixed in python-crypto 2.6.1-4 has caused the Debian Bug report #740086, regarding python3-crypto: Ships files which are also present in python3-crypto-dbg to be marked as done. This means that you cl

Processed: Fixed in unstable

Processing commands for cont...@bugs.debian.org: > fixed 740111 1.4.2-1 Bug #740111 [icedtea-netx] icedtea-netx: NullPointerException in SwingUtilities.appContextGet Marked as fixed in versions icedtea-web/1.4.2-1. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#740111: Fixed in unstable

fixed 740111 1.4.2-1 thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#740117: haveged: spinning

Package: haveged Version: 1.7c-1 Severity: grave Justification: renders package unusable Haveged is just spinning and not comming anywhere :( Been watching it for hours doing that. Uses one CPU at 100%. Upstream version 1.9.0 promisses improvements, although I have no idea if those address the pr

Processed: Re: Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg

Processing commands for cont...@bugs.debian.org: > notfound 740053 python-coverage/3.7+dfsg.1-4 Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg No longer marked as found in versions python-coverage/3.7+dfsg.1-4. > found 740053 python3-coverage/3.7+dfsg.1-4

Processed (with 1 errors): Re: Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg

Processing commands for cont...@bugs.debian.org: > package python-coverage Limiting to bugs with field 'package' containing at least one of 'python-coverage' Limit currently set to 'package':'python-coverage' > notfound 740053 python-coverage/3.7+dfsg.1-4 package: "python3-coverage"' does not ma

Processed: Re: Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg

Processing commands for cont...@bugs.debian.org: > package python3-coverage Limiting to bugs with field 'package' containing at least one of 'python3-coverage' Limit currently set to 'package':'python3-coverage' > notfound 740053 python3-coverage/3.7+dfsg.1-4 Bug #740053 [python3-coverage] pytho

Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg

package python3-coverage notfound 740053 python3-coverage/3.7+dfsg.1-4 found 740053 python3-coverage/3.7+dfsg.1-4+b1 tags 740053 + confirmed thanks On 25-Feb-2014, Dmitry Shachnev wrote: > Today’s update of python3-coverage (Which is “3.7+dfsg.1-4+b1”; I'm updating the bug report accordingly.) >

Processed: Fixed in unstable

Processing commands for cont...@bugs.debian.org: > notfound 740111 1.4.2-1 Bug #740111 [icedtea-netx] icedtea-netx: NullPointerException in SwingUtilities.appContextGet Ignoring request to alter found versions of bug #740111 to the same values previously set > thanks Stopping processing here. P

Bug#740111: Fixed in unstable

notfound 740111 1.4.2-1 thanks The problem does not happen with 1.4.2-1, currently in unstable. Works well with both openjdk 6 and 7. Sidenote: trying to install 1.4-3~deb7u2, it wanted to deinstall icedtea-6-plugin, so I did not test that one after all. Isn't that another bug ? -- To UNSUBSC

Bug#740111: icedtea-netx: NullPointerException in SwingUtilities.appContextGet

Package: icedtea-netx Version: 1.3.2-1 Severity: serious Tring to understand why the KGS Go client at http://files.gokgs.com/javaBin/cgoban.jnlp would not start: * default javaws (using openjdk-6) even explodes when passed no argument: $ /usr/lib/jvm/java-6-openjdk-amd64/bin/javaws Exception in

Bug#738413: marked as done (ubuntu-dev-tools: FTBFS: Tests failed)

Your message dated Tue, 25 Feb 2014 21:29:28 + with message-id and subject line Bug#738413: fixed in ubuntu-dev-tools 0.152+nmu1 has caused the Debian Bug report #738413, regarding ubuntu-dev-tools: FTBFS: Tests failed to be marked as done. This means that you claim that the problem has been

Bug#738378: marked as done (freecontact: FTBFS: configure: error: Could not find a version of the library!)

Your message dated Tue, 25 Feb 2014 21:22:05 + with message-id and subject line Bug#738378: fixed in freecontact 1.0.21-3 has caused the Debian Bug report #738378, regarding freecontact: FTBFS: configure: error: Could not find a version of the library! to be marked as done. This means that y

Processed: Re: Bug#734268: linux-image-3.12-1-amd64: NFS-related crashes

Processing control commands: > severity -1 critical Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Severity set to 'critical' from 'important' > found -1 linux/3.12.6-2 Bug #734268 [src:linux] linux-image-3.12-1-amd64: NFS-related crashes Marked as found in versions linux/3.

Bug#738432: thin: looks for vendor_ruby multiarch libs in wrong location

Control: severity 737032 serious Control: merge -1 737032 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: thin: looks for vendor_ruby multiarch libs in wrong location

Processing control commands: > severity 737032 serious Bug #737032 [thin] thin: looks for vendor_ruby multiarch libs in wrong location Severity set to 'serious' from 'important' > merge -1 737032 Bug #738432 [thin] ruby-vegas: FTBFS: ERROR: Test "ruby2.0" failed: LoadError: cannot load such file

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tag 740086 + pending Bug #740086 [python3-crypto] python3-crypto: Ships files which are also present in python3-crypto-dbg Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 740086: http://bugs

Processed: retitle 739589 to multiple security flaws in migration stream processing

Processing commands for cont...@bugs.debian.org: > retitle 739589 multiple security flaws in migration stream processing Bug #739589 [qemu] qemu: Multiple security issues Changed Bug title to 'multiple security flaws in migration stream processing' from 'qemu: Multiple security issues' > thanks S

Processed (with 1 errors): thin: looks for vendor_ruby multiarch libs in wrong location

Processing control commands: > reassign -1 thin 1.3.1-4 Bug #738432 [src:ruby-vegas] ruby-vegas: FTBFS: ERROR: Test "ruby2.0" failed: LoadError: cannot load such file -- /usr/lib/ruby/vendor_ruby/2.0.0/x86_64-linux-gnu/thin_parser Bug reassigned from package 'src:ruby-vegas' to 'thin'. No longer

Bug#740106: libraw: FTBFS on 32-bit platforms: symbols not quite as expected

Source: libraw Version: 0.15.4-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of libraw on 32-bit platforms such as i386 have been failing, because it winds up defining slightly different symbols than on 64-bit platforms, even with the (c+

Bug#738432: thin: looks for vendor_ruby multiarch libs in wrong location

Control: reassign -1 thin 1.3.1-4 Control: merge -1 737032 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

On 2014-02-25 17:56, Cyril Brulebois wrote: > Cyril Brulebois (2014-02-13): >> [...] >> Failing a short resolution, I'm tempted to pretend sparc isn't an issue, >> and maybe ask for a migration to testing + dak copy-installer. >> >> @debian-release: would that sound reasonable? > > Ping? > > [..

Bug#740047: [Pkg-libvirt-maintainers] Bug#740047: virt-manager: lost all connections on upgrade to experimental

Hi Paul, On Tue, Feb 25, 2014 at 03:11:26PM +0800, Paul Wise wrote: > On Tue, 2014-02-25 at 14:57 +0800, Paul Wise wrote: > > > When I upgraded virt-manager from unstable to experimental, virt-manager > > forgot all the connection details I had stored. > > When I downgraded back to the version in

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

On Thu, Feb 13, 2014 at 04:38:36PM +0300, Cyril Brulebois wrote: > [ TL;DR: d-i FTBFS on sparc, what do we do now? ] > > Thomas Schmitt (2013-12-10): > > Cyril Brulebois wrote: > > > genisoimage: Error: './tmp/miniiso/cd_tree/boot/.' and > > > './tmp/miniiso/cd_tree/boot/..' have the same ISO9660

Bug#740097: nvidia-legacy-304xx-kernel-source: Module can not be loaded for Linux 3.13

Package: nvidia-legacy-304xx-kernel-source Version: 304.117-1 Severity: grave Justification: renders package unusable Upgrade to linux-image-3.13-1-amd64 made the nvidia module build fine by DKMS, but loading failes with the dmesg entry: kernel: nvidia: Unknown symbol acpi_os_wait_events_complete

Bug#734894: marked as done (libopenni-sensor-primesense0: modifies conffiles (policy 10.7.3): /etc/openni/modules.xml)

Your message dated Tue, 25 Feb 2014 17:04:23 + with message-id and subject line Bug#734894: fixed in openni 1.5.4.0-7 has caused the Debian Bug report #734894, regarding libopenni-sensor-primesense0: modifies conffiles (policy 10.7.3): /etc/openni/modules.xml to be marked as done. This means

Bug#734768: marked as done (libopenni-sensor-pointclouds0: modifies conffiles (policy 10.7.3): /etc/openni/modules.xml)

Your message dated Tue, 25 Feb 2014 17:04:23 + with message-id and subject line Bug#734768: fixed in openni 1.5.4.0-7 has caused the Debian Bug report #734768, regarding libopenni-sensor-pointclouds0: modifies conffiles (policy 10.7.3): /etc/openni/modules.xml to be marked as done. This mean

Bug#731806: debian-installer: FTBFS on sparc: genisoimage errors

Cyril Brulebois (2014-02-13): > [ TL;DR: d-i FTBFS on sparc, what do we do now? ] > > @Kurt: did anything change on the buildd setup side? Both lebrun and spontini > got that FTBFS, while that wasn't the case before: > https://buildd.debian.org/status/logs.php?pkg=debian-installer&arch=sparc P

Bug#740086: python3-crypto: Ships files which are also present in python3-crypto-dbg

Package: python3-crypto Version: 2.6.1-3 Severity: serious Justification: uninstallable on arm archs Dear Maintainer, Currently python3-crypto ships debug extension files on arm*, which makes it uninstallable together with python3-crypto-dbg. See e.g.: https://packages.debian.org/sid/armhf/pytho

Processed: merging 734523 740064

Processing commands for cont...@bugs.debian.org: > merge 734523 740064 Bug #734523 [dhelp] dhelp: Error while building the HTML tree Bug #740064 [dhelp] dhelp: Weekly cron job always fails. Merged 734523 740064 > thanks Stopping processing here. Please contact me if you need assistance. -- 73452

Bug#736392: octave-plplot: FTBFS with Octave 3.8

Am 25.02.2014 12:08, schrieb Matthias Klose: > trying to fix this in Ubuntu trusty (14.04), ... > > - applied the octave patch in swig2.0 (2.0.11-1ubuntu2) > - plplot still fails to build, apparently with the >very same error messages. >https://launchpad.net/ubuntu/+source/plplot/5.9.9-5

Bug#738569: gpointing-device-settings: Segfaults at startup, cannot get it to work

On Mon, Feb 10, 2014 at 12:18 -0600, Gunnar Wolf wrote: > All the output I get from running this is: > > $ gpointing-device-settings > Segmentation fault Valgrind reports several functions accessing memory that's already been free'd by gpds_xinput_utils_get_device_info(), and that functi

Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg

Control: tags -1 patch >From the build log I noticed that this is an issue in python3_objcode_versions definition: dh [...] --exclude .cpython-3433dm-i386-linux-gnu.so Attaching a patch that should fix the issue. -- Dmitry Shachnev--- a/debian/rules +++ b/debian/rules @@ -28,7 +28,7 @@ # w

Processed: Re: python3-coverage: overwrites file in python3-coverage-dbg

Processing control commands: > tags -1 patch Bug #740053 [python3-coverage] python3-coverage: overwrites file in python3-coverage-dbg Added tag(s) patch. -- 740053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -

Bug#738961: synaptic: Application is closing at the moment that any key is pressed

Dear Vogt, I run the debugging command and now is perfectly working! I couldn't make it crash. I'm so sorry, how ever is working fine. Also I have make a lot of updates, upgrades, so I'm not sure what happened. Let me know If can do something else for you! best regards On 20 February 2014 08:16

Bug#733352: [Debian-med-packaging] Bug#733352: Bowtie and tophat fail to build with seqan >= 1.4

На 25.2.2014 г. 15:30 ч., Andreas Tille написа: since we uploaded seqan 1.4.x packages to Debian the packages bowtie and tophat failed to build while the build went fine with seqan 1.3. Please also let us know if you have no idea how to fix this. In this case we would use a last fallback and

Bug#733352: Bowtie and tophat fail to build with seqan >= 1.4

Hi Manuel, since we uploaded seqan 1.4.x packages to Debian the packages bowtie and tophat failed to build while the build went fine with seqan 1.3. Since I personally have no idea how to fix this and neither bowtie nor tophat developers answered to our request I wonder whether some seqan develop

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 739998 maven-repo-helper Bug #739998 [src:cobertura] cobertura: FTBFS: Maven error Bug reassigned from package 'src:cobertura' to 'maven-repo-helper'. No longer marked as found in versions cobertura/1.8.6 and cobertura/1.9.4.1+dfsg-3. Ig

Bug#738424: marked as done (libraw: FTBFS: dpkg-gensymbols failures)

Your message dated Tue, 25 Feb 2014 12:00:07 + with message-id and subject line Bug#738424: fixed in libraw 0.16.0-1 has caused the Debian Bug report #738424, regarding libraw: FTBFS: dpkg-gensymbols failures to be marked as done. This means that you claim that the problem has been dealt with

Bug#736392: octave-plplot: FTBFS with Octave 3.8

Am 25.02.2014 12:08, schrieb Matthias Klose: > trying to fix this in Ubuntu trusty (14.04), ... > > - applied the octave patch in swig2.0 (2.0.11-1ubuntu2) same with swig 2.0.12. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Cont

Bug#736392: octave-plplot: FTBFS with Octave 3.8

trying to fix this in Ubuntu trusty (14.04), ... - applied the octave patch in swig2.0 (2.0.11-1ubuntu2) - plplot still fails to build, apparently with the very same error messages. https://launchpad.net/ubuntu/+source/plplot/5.9.9-5ubuntu8 Is there anything additional needed? Thanks, Ma

Processed (with 2 errors): your mail

Processing commands for cont...@bugs.debian.org: > reassign maven-repo-helper 740001 74 739998 Unknown command or malformed arguments to command. > found 739998 1.8.6 Bug #739998 [src:cobertura] cobertura: FTBFS: Maven error The source 'cobertura' and version '1.8.6' do not appear to match any

Bug#740064: dhelp: Weekly cron job always fails.

Package: dhelp Version: 0.6.21+nmu3 Severity: grave Justification: renders package unusable Dear Maintainer, I will paste (last) mail I received - I received one each week. I didn't change standard configuration of this package so it is failing by default. I also deleted this package recently as

Bug#738393: Probably related to Tilt API changes

severity 738393 normal affects 738488 camping usertag 738393 +will-break-if-tilt-2.0-is-uploaded thanks Hi, I'm pretty sure (looking at the timeline) that the build issues were due to Tilt suddenly changing it's API. This was fixed by a reupload of ruby-tilt 2.0.0+really1.4.1-1 but will break Ca

Processed: Probably related to Tilt API changes

Processing commands for cont...@bugs.debian.org: > severity 738393 normal Bug #738393 [src:camping] camping: FTBFS: ERROR: Test "ruby1.9.1" failed. Severity set to 'normal' from 'serious' > affects 738488 camping Bug #738488 {Done: Antonio Terceiro } [ruby-tilt] ruby-tilt: Broke compatibility wit

Bug#739989: debian-installer-utils: log-output change breaks speech synthesis

On Tue, Feb 25, 2014 at 09:10:38AM +0300, Cyril Brulebois wrote: > Did you see my follow-up mail[1]? It looks to me it does not only trigger > the espeakup hang, but a whole bunch of other hangs. I did, but without data I didn't have time to trawl through looking for them. I'm not asserting that

Bug#738392: marked as done (proofgeneral: FTBFS: Latex errors)

Your message dated Tue, 25 Feb 2014 09:20:02 + with message-id and subject line Bug#738392: fixed in proofgeneral 4.3~pre130510-1.1 has caused the Debian Bug report #738392, regarding proofgeneral: FTBFS: Latex errors to be marked as done. This means that you claim that the problem has been d

Bug#738811: handbrake: crashes after source DVD is selected

Am Dienstag, den 25.02.2014, 09:51 +0100 schrieb Jan Korous: > That's funny. I didn't notice this option. As soon as I unchecked the > box (and started using libdvdread) it works. So the problem was in > dvdnav actually (or at least according to the checker box label). Let's hope new new releases

Bug#738811: handbrake: crashes after source DVD is selected

That's funny. I didn't notice this option. As soon as I unchecked the box (and started using libdvdread) it works. So the problem was in dvdnav actually (or at least according to the checker box label). On Tue, Feb 25, 2014 at 7:53 AM, Dmitry Smirnov wrote: > Are you using "dvdnav" or "libdvdrea

Bug#740053: python3-coverage: overwrites file in python3-coverage-dbg

Package: python3-coverage Version: 3.7+dfsg.1-4 Severity: serious Justification: fails to install/upgrade Dear Maintainer, Today’s update of python3-coverage failed with: | Unpacking python3-coverage (3.7+dfsg.1-4+b1) over (3.7+dfsg.1-4) ... | dpkg: error processing archive /var/cache/apt/archi