Processed: Re: Bug#748816: qtmultimedia-opensource-src: FTBFS on kfreebsd-*

Processing commands for cont...@bugs.debian.org: > severity 748816 important Bug #748816 [qtmultimedia-opensource-src] qtmultimedia-opensource-src: FTBFS on kfreebsd-* Severity set to 'important' from 'serious' > tag 748816 + pending Bug #748816 [qtmultimedia-opensource-src] qtmultimedia-opensour

Bug#748816: qtmultimedia-opensource-src: FTBFS on kfreebsd-*

severity 748816 important tag 748816 + pending thanks On 2014-05-21 03:05, Steven Chamberlain wrote: Package: qtmultimedia-opensource-src Version: 5.2.1-3 Severity: serious Note that qtmultimedia-opensource-src has never built on kfreebsd so far (or on any non-linux architecture, for what co

Bug#748832: package does not work at all: Unable to load subvertpy extensions: cannot import name client

Package: python-subvertpy Severity: serious Version: 0.9.1-5 Hello, I was investigating current autopkgtest failures and I stumbled over http://ci.debian.net/#package/subvertpy which fails with File "subvertpy/__init__.py", line 131, in raise ImportError("Unable to load subvertpy exte

Bug#748828: collabtive: CVE-2014-3246 CVE-2014-3247

Source: collabtive Severity: grave Tags: security upstream Hi, the following vulnerabilities were published for collabtive. CVE-2014-3246[0]: | SQL injection vulnerability in Collabtive 1.2 allows remote | authenticated users to execute arbitrary SQL commands via the folder | parameter in a file

Bug#748827: torque: CVE-2014-0749

Source: torque Version: 2.4.8+dfsg-9 Severity: grave Tags: security upstream Hi, the following vulnerability was published for torque. CVE-2014-0749[0]: | Stack-based buffer overflow in lib/Libdis/disrsi_.c in Terascale | Open-Source Resource and Queue Manager (aka TORQUE Resource Manager) | 2.5

Bug#748816: qtmultimedia-opensource-src: FTBFS on kfreebsd-*

Package: qtmultimedia-opensource-src Version: 5.2.1-3 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd Hi, qtmultimedia-opensource-src FTBFS on kfreebsd-* at the dh_shlibdeps stage. The apparently missing file libfftreal.so.1 is in the same directory as the spectrum executa

Bug#748742: liferea: Crashes some seconds after launch even without user interaction (segfault in libpthread)

On 05/20/2014 06:37 AM, Andrea Lusuardi wrote: > Package: liferea > Version: 1.10.8-1 > Severity: grave > Justification: renders package unusable > > Hi, > the package liferea crashes predictably after 3 to 10 seconds from launch, in > the dmesg > i can see the problem as follows: > > [46072.157

Bug#601106: marked as done (gdm3: On kfreebsd 'New Login in a Window' (gdmflexiserver --xnest) does not work.)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#733546: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #733546, regarding gdm3: On kfreebsd 'New Login in a Window' (gdmflexiserver --xnest) does not work. to be marked as done. This means that you c

Bug#612157: marked as done (gdm3: gdm-session-worker hangs on kfreebsd-i386)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#612157: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #612157, regarding gdm3: gdm-session-worker hangs on kfreebsd-i386 to be marked as done. This means that you claim that the problem has been deal

Bug#602724: marked as done (gdm3: login problem in kfreebsd-i386)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#733546: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #733546, regarding gdm3: login problem in kfreebsd-i386 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#747292: marked as done (gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#747210: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #747210, regarding gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session to be marked as done. This means t

Bug#733546: marked as done (gdm3: stuck on GNU/kFreeBSD while "trying to open reauthentication channel")

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#612157: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #612157, regarding gdm3: stuck on GNU/kFreeBSD while "trying to open reauthentication channel" to be marked as done. This means that you claim t

Bug#612157: marked as done (gdm3: gdm-session-worker hangs on kfreebsd-i386)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#733546: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #733546, regarding gdm3: gdm-session-worker hangs on kfreebsd-i386 to be marked as done. This means that you claim that the problem has been deal

Bug#602724: marked as done (gdm3: login problem in kfreebsd-i386)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#602724: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #602724, regarding gdm3: login problem in kfreebsd-i386 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#733546: marked as done (gdm3: stuck on GNU/kFreeBSD while "trying to open reauthentication channel")

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#602724: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #602724, regarding gdm3: stuck on GNU/kFreeBSD while "trying to open reauthentication channel" to be marked as done. This means that you claim t

Bug#733546: marked as done (gdm3: stuck on GNU/kFreeBSD while "trying to open reauthentication channel")

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#733546: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #733546, regarding gdm3: stuck on GNU/kFreeBSD while "trying to open reauthentication channel" to be marked as done. This means that you claim t

Bug#733546: marked as done (gdm3: stuck on GNU/kFreeBSD while "trying to open reauthentication channel")

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#601106: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #601106, regarding gdm3: stuck on GNU/kFreeBSD while "trying to open reauthentication channel" to be marked as done. This means that you claim t

Bug#601106: marked as done (gdm3: On kfreebsd 'New Login in a Window' (gdmflexiserver --xnest) does not work.)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#612157: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #612157, regarding gdm3: On kfreebsd 'New Login in a Window' (gdmflexiserver --xnest) does not work. to be marked as done. This means that you c

Bug#602724: marked as done (gdm3: login problem in kfreebsd-i386)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#612157: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #612157, regarding gdm3: login problem in kfreebsd-i386 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#612157: marked as done (gdm3: gdm-session-worker hangs on kfreebsd-i386)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#602724: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #602724, regarding gdm3: gdm-session-worker hangs on kfreebsd-i386 to be marked as done. This means that you claim that the problem has been deal

Bug#601106: marked as done (gdm3: On kfreebsd 'New Login in a Window' (gdmflexiserver --xnest) does not work.)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#602724: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #602724, regarding gdm3: On kfreebsd 'New Login in a Window' (gdmflexiserver --xnest) does not work. to be marked as done. This means that you c

Bug#612157: marked as done (gdm3: gdm-session-worker hangs on kfreebsd-i386)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#601106: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #601106, regarding gdm3: gdm-session-worker hangs on kfreebsd-i386 to be marked as done. This means that you claim that the problem has been deal

Bug#602724: marked as done (gdm3: login problem in kfreebsd-i386)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#601106: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #601106, regarding gdm3: login problem in kfreebsd-i386 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#601106: marked as done (gdm3: On kfreebsd 'New Login in a Window' (gdmflexiserver --xnest) does not work.)

Your message dated Tue, 20 May 2014 22:03:49 + with message-id and subject line Bug#601106: fixed in gdm3 3.12.2-1 has caused the Debian Bug report #601106, regarding gdm3: On kfreebsd 'New Login in a Window' (gdmflexiserver --xnest) does not work. to be marked as done. This means that you c

Processed: control

Processing commands for cont...@bugs.debian.org: > reassign 664988 libpcre3 Bug #664988 [emacs23] emacs23 failed on update due to missing library libpcre.so.3 Bug reassigned from package 'emacs23' to 'libpcre3'. No longer marked as found in versions emacs23/23.4+1-2. Ignoring request to alter fix

Bug#748751: marked as done (missing license in debian/copyright)

Your message dated Tue, 20 May 2014 21:53:05 + with message-id and subject line Bug#748751: fixed in tulip 4.5.0dfsg-2 has caused the Debian Bug report #748751, regarding missing license in debian/copyright to be marked as done. This means that you claim that the problem has been dealt with.

Processed: fix versions for 746049

Processing commands for cont...@bugs.debian.org: > # found and fixed version not in same package > reassign 746049 vala-0.24 Bug #746049 {Done: Andreas Henriksson } [src:gucharmap] gucharmap: FTBFS: Gucharmap-2.90.gir:1424.7-1424.33: error: The type name `Atk.TableCell' could not be found Bug re

Bug#747292: marked as done (gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session)

Your message dated Tue, 20 May 2014 21:19:22 + with message-id and subject line Bug#747210: fixed in gdm3 3.8.4-9 has caused the Debian Bug report #747210, regarding gdm3: Unable to login after last upgrade (version 3.8.4-7): fails to start a GNOME session to be marked as done. This means th

Bug#743439: lxsession: Reboot and Shutdown does not work with systemd-sysv and lightdm

Package: lxsession Version: 0.4.9.2-1 Followup-For: Bug #743439 Another party affected here. I have also the same version and I can't shutdown the computer with the default package. This is problematic since systemd is required in ordrer to mount the removable peripherical (is that a dependcy fro

Processed: found 726799 in shared-mime-info/1.0-1+b1, found 726799 in shared-mime-info/1.3-1

Processing commands for cont...@bugs.debian.org: > found 726799 shared-mime-info/1.0-1+b1 Bug #726799 [shared-mime-info] update-mime-database.real deletes files installed by other packages The source shared-mime-info and version 1.0-1+b1 do not appear to match any binary packages Marked as found

Processed: tagging 747789

Processing commands for cont...@bugs.debian.org: > tags 747789 + patch pending Bug #747789 [src:jitsi] jitsi: FTBFS: error: package org.json.simple does not exist Added tag(s) pending and patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 747789: http://bugs.

Processed (with 2 errors): Re: Bug#726799: qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml

Processing commands for cont...@bugs.debian.org: > reassign 726799 shared-mime-info Bug #726799 [qgo] qgo: deletes a shipped file during upgrades: /usr/share/mime/text/x-sgf.xml Bug reassigned from package 'qgo' to 'shared-mime-info'. No longer marked as found in versions qgo/2.0~git-20130914-1 a

Processed: found 739432 in 2.4.4997-1, closing 739432

Processing commands for cont...@bugs.debian.org: > found 739432 2.4.4997-1 Bug #739432 [src:jitsi] jitsi: FTBFS with libav10 Marked as found in versions jitsi/2.4.4997-1. > close 739432 2.4.4997-1.1 Bug #739432 [src:jitsi] jitsi: FTBFS with libav10 Marked as fixed in versions jitsi/2.4.4997-1.1. B

Bug#747789: jitsi: diff for NMU version 2.4.4997-1.2

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

Bug#748574: 3.14.1 does not boot on Dell server

Le 20/05/2014 21:16, Erwan David a écrit : > I do not see how to apply the patch you provided once I got the source > of the package. > > patch < 00*.patch does nit find the file to patch whether I use it in > the directory where I got the source package or in the linux-3.14-1 > subdirectory > > So

Bug#747428: [xbmc] passwords are stored in plain xml file

Hi, CVE-2014-3800 was assigned now for the issue that mode 0644 is used for the file containing the password, see [1]. [1] http://www.openwall.com/lists/oss-security/2014/05/20/5 Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubs

Processed: tagging 747789

Processing commands for cont...@bugs.debian.org: > tags 747789 - jessie sid Bug #747789 [src:jitsi] jitsi: FTBFS: error: package org.json.simple does not exist Removed tag(s) sid and jessie. > thanks Stopping processing here. Please contact me if you need assistance. -- 747789: http://bugs.debi

Bug#747862: marked as done (proj-data: Package contains architecture dependent files in /usr/share)

Your message dated Tue, 20 May 2014 19:19:27 + with message-id and subject line Bug#747862: fixed in proj 4.8.0-5 has caused the Debian Bug report #747862, regarding proj-data: Package contains architecture dependent files in /usr/share to be marked as done. This means that you claim that the

Bug#748574: 3.14.1 does not boot on Dell server

I do not see how to apply the patch you provided once I got the source of the package. patch < 00*.patch does nit find the file to patch whether I use it in the directory where I got the source package or in the linux-3.14-1 subdirectory signature.asc Description: OpenPGP digital signature

Bug#748789: view3dscene: FTBFS Can't find unit CastleStringUtils used by CastleUtils

Package: view3dscene Version: 3.13.0-2 Severity: serious Tags: pending Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 As already discussed [1] on the pkg-pas...@lists.alioth.debian.org e-mail list, the current versio

Bug#748367: visp: diff for NMU version 2.8.0-5.1

Control: tags -1 + pending Dear Maintainer, to move forward with the libav transition, I've prepared an NMU for visp (versioned as 2.8.0-5.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru visp-2.8.0/debian/changelog

Processed: visp: diff for NMU version 2.8.0-5.1

Processing control commands: > tags -1 + pending Bug #748367 [src:visp] visp: FTBFS with libav10 Added tag(s) pending. -- 748367: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748367 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bu

Processed: NMU for dhelp

Processing control commands: > tags 734523 + pending Bug #734523 [dhelp] dhelp: Error while building the HTML tree Bug #740064 [dhelp] dhelp: Weekly cron job always fails. Added tag(s) pending. Added tag(s) pending. > tags 732916 + pending Bug #732916 [dhelp] Depends on obsolete package: ruby1.8 A

Processed: NMU for dhelp

Processing control commands: > tags 734523 + pending Bug #734523 [dhelp] dhelp: Error while building the HTML tree Bug #740064 [dhelp] dhelp: Weekly cron job always fails. Ignoring request to alter tags of bug #734523 to the same tags previously set Ignoring request to alter tags of bug #740064 to

Processed: NMU for dhelp

Processing control commands: > tags 734523 + pending Bug #734523 [dhelp] dhelp: Error while building the HTML tree Bug #740064 [dhelp] dhelp: Weekly cron job always fails. Ignoring request to alter tags of bug #734523 to the same tags previously set Ignoring request to alter tags of bug #740064 to

Bug#712621: NMU for dhelp

Control: tags 734523 + pending Control: tags 732916 + pending Control: tags 712621 + pending Dear maintainer, I've prepared an NMU for dhelp (versioned as 0.6.21+nmu4) fixing this bugs and uploaded it to DELAYED/2. Please feel

Processed: jitsi: this isn't the FTBFS, #747789 is

Processing control commands: > retitle -1 jitsi: documentation not built Bug #748503 [src:jitsi] jitsi: FTBFS: error: unmappable character for encoding error: unmappable character for encoding ASCII Changed Bug title to 'jitsi: documentation not built' from 'jitsi: FTBFS: error: unmappable char

Bug#748503: jitsi: this isn't the FTBFS, #747789 is

Control: retitle -1 jitsi: documentation not built Control: tags -1 jessie sid Control: severity -1 normal jitsi has always had these "error: unmappable character for encoding error: unmappable character for encoding ASCII " messages (due to non-ASCII characters in comments), but though they co

Processed: bug 747740 is forwarded to https://github.com/mkdynamic/omniauth-facebook/issues/153

Processing commands for cont...@bugs.debian.org: > forwarded 747740 https://github.com/mkdynamic/omniauth-facebook/issues/153 Bug #747740 [src:ruby-omniauth-facebook] FTBFS: Test "ruby2.1" failed. Exiting. Set Bug forwarded-to-address to 'https://github.com/mkdynamic/omniauth-facebook/issues/153'

Processed: control

Processing commands for cont...@bugs.debian.org: > reassign 171736 emacs21 Bug #171736 [emacs21-common] emacs21-common: custom-make-dependencies sort breakage Warning: Unknown package 'emacs21-common' Bug reassigned from package 'emacs21-common' to 'emacs21'. Warning: Unknown package 'emacs21' Wa

Bug#748574: 3.14.1 does not boot on Dell server

On 05/18/2014 09:25 PM, Ben Hutchings wrote: Please test whether the attached patch fixes this, following the instructions at Ben. /boot had become a mess with on me so I cleaned it out and re-installed the

Processed (with 1 errors): control

Processing commands for cont...@bugs.debian.org: > unarchive 166139 Bug #166139 {Done: Rob Browning } [emacs21] FTBFS: Build failure of w3-el-e21 on i386 Bug #166277 {Done: Rob Browning } [emacs21] FTBFS: Build failure of w3-url-e21 on i386 Bug #173113 {Done: Rob Browning } [emacs21] FTBFS: Buil

Bug#748776: libprelude: FTBFS on armel and armhf but build there in the past

Source: libprelude Version: 1.0.0-11.1 Severity: serious Hi, The most recent upload of libprelude seems to FTBFS on armel and armhf. It seems to caused by a seg. fault in the test suite. The relevant part of the log appears to be: """ libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector --p

Bug#748775: Should not be released with jessie

Source: libnl Version: 1.1-8 Severity: serious This is a blocker bug to ensure jessie is not released with libnl1. It's no longer developed and superseded by libnl3. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') A

Bug#730962: marked as done (libzip-ruby: FTBFS: /usr/bin/ruby1.8: No such file or directory -- debian-setup.rb (LoadError))

Your message dated Tue, 20 May 2014 17:00:07 + with message-id and subject line Bug#730962: fixed in ruby-zip 1.1.2-1 has caused the Debian Bug report #730962, regarding libzip-ruby: FTBFS: /usr/bin/ruby1.8: No such file or directory -- debian-setup.rb (LoadError) to be marked as done. This

Bug#722367: marked as done (Depends on Ruby 1.8 which will not be available in jessie)

Your message dated Tue, 20 May 2014 17:00:07 + with message-id and subject line Bug#722367: fixed in ruby-zip 1.1.2-1 has caused the Debian Bug report #722367, regarding Depends on Ruby 1.8 which will not be available in jessie to be marked as done. This means that you claim that the problem

Bug#747801: marked as done (ario: FTBFS: error: Missing dependency: libgcrypt)

Your message dated Tue, 20 May 2014 16:48:38 + with message-id and subject line Bug#747801: fixed in ario 1.5.1-1.2 has caused the Debian Bug report #747801, regarding ario: FTBFS: error: Missing dependency: libgcrypt to be marked as done. This means that you claim that the problem has been d

Bug#748770: gpiv: FTBFS on s390x (format not a string literal and no format arguments)

Source: gpiv Version: 0.6.1-2.1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on s390x: > mpicc -DPACKAGE_NAME=\"gpiv\" -DPACKAGE_TARNAME=\"gpiv\" > -DPACKAGE_VERSION=\"0.6.1\" -DPACKAGE_STRING=\"gpiv\ 0.6.1\"

Bug#748769: aces3: FTBFS on s390x (recipe for target 'errorhl.o' failed)

Source: aces3 Version: 3.0.6-7 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags: jessie sid Hi, your package no longer builds on s390x: > mpicxx -c -DMPIF2C -DMPI2 -DC_SUFFIX -DCB_SUFFIX -g -O2 -Wall -I../include > -I../sip -I../aces2/include

Bug#748650: marked as done (vmdebootstrap: uninstallable with current extlinux in unstable)

Your message dated Tue, 20 May 2014 15:47:59 + with message-id and subject line Bug#748650: fixed in vmdebootstrap 0.2-3 has caused the Debian Bug report #748650, regarding vmdebootstrap: uninstallable with current extlinux in unstable to be marked as done. This means that you claim that the

Bug#739460: marked as done (openscenegraph: FTBFS with libav10)

Your message dated Tue, 20 May 2014 15:45:47 + with message-id and subject line Bug#739460: fixed in openscenegraph 3.2.0~rc1-5.1 has caused the Debian Bug report #739460, regarding openscenegraph: FTBFS with libav10 to be marked as done. This means that you claim that the problem has been de

Bug#613169: status

Michael Biebl wrote: > This bug has been open for a while and is now blocking the removal of > hal [0]. What's your plan regarding sleepd? Do you still want to port it > to some newer/other interfaces or should the package be removed from the > archive? I have no plans for sleepd. -- see shy jo

Bug#748761: printer-driver-gutenprint: Cups doesn't print because rastertogutenprint.5.2 is missing

Package: printer-driver-gutenprint Version: 5.2.10~pre2-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, installing printer-driver-gutenprint (5.2.10~pre2-1) break cups. The error reported is: file "/usr/lib/cups/filter/rastertogutenprint.5.2" not available

Bug#748749: src:xapian-bindings: Build-Depends on ruby2.0, which will not be shipped in jessie

tags 748749 + pending thanks On Tue, May 20, 2014 at 09:48:35AM -0300, Antonio Terceiro wrote: > To always build for the supported Ruby versions, you should probably > just drop `ruby, ruby2.0-dev, ruby2.1-dev, ruby2.0, ruby2.1` in the > Build-Depends field since `ruby-all-dev` will already pull i

Processed: Re: Bug#748749: src:xapian-bindings: Build-Depends on ruby2.0, which will not be shipped in jessie

Processing commands for cont...@bugs.debian.org: > tags 748749 + pending Bug #748749 [src:xapian-bindings] src:xapian-bindings: Build-Depends on ruby2.0, which will not be shipped in jessie Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 748

Processed: try harder to match the -dev packages too

Processing commands for cont...@bugs.debian.org: > reassign 748661 src:meep-lam4 Bug #748661 [meep-lam4] meep-lam4: fails to upgrade from wheezy - trying to overwrite ... Bug reassigned from package 'meep-lam4' to 'src:meep-lam4'. No longer marked as found in versions meep-lam4/1.2.1-1. Ignoring

Bug#746490: marked as done (python-carrierwave ftbfs in unstable)

Your message dated Tue, 20 May 2014 18:33:05 +0530 with message-id <537b5289.3040...@debian.org> and subject line ruby-fog 1.22.0-2 depends on ruby-fog-core has caused the Debian Bug report #746490, regarding python-carrierwave ftbfs in unstable to be marked as done. This means that you claim that

Processed: block 746490 with 746123

Processing commands for cont...@bugs.debian.org: > block 746490 with 746123 Bug #746490 [ruby-carrierwave] python-carrierwave ftbfs in unstable 746490 was not blocked by any bugs. 746490 was not blocking any bugs. Added blocking bug(s) of 746490: 746123 > thanks Stopping processing here. Please c

Bug#734318: marked as done (tulip: [amd64] segfaults inside dlopen when loading plugins)

Your message dated Tue, 20 May 2014 13:00:25 + with message-id and subject line Bug#734318: fixed in tulip 4.5.0dfsg-1 has caused the Debian Bug report #734318, regarding tulip: [amd64] segfaults inside dlopen when loading plugins to be marked as done. This means that you claim that the probl

Bug#748751: missing license in debian/copyright

Package: tulip Version: 4.5.0dfsg-1 Severity: serious User: alteh...@debian.org Usertags: ftp X-Debbugs-CC: ftpmas...@ftp-master.debian.org thanks Dear Maintainer, please add the missing licenses of: plugins/import/facebook/facebook.py FindSIP.py doc/common/_static/customized.css to debian/co

Bug#748750: src:mhc: Build-Depends on ruby2.0, which will not be shipped in jessie

Package: src:mhc Version: 0.25.1+20130926-2 Severity: serious ruby2.0 will not be shipped with Jessie. To always build to the supported Ruby version(s), you can replace `ruby2.0, ruby2.0-dev` in the Build-Depends field with `ruby-dev`, which will always pull in the development files for the curre

Bug#748749: src:xapian-bindings: Build-Depends on ruby2.0, which will not be shipped in jessie

Package: src:xapian-bindings Version: 1.2.17-2 Severity: serious Hello, xapian-bindings build depends on ruby2.0 but it will not be shipped in jessie. Please drop that build dependency. To always build for the supported Ruby versions, you should probably just drop `ruby, ruby2.0-dev, ruby2.1-dev

Bug#733407: marked as done (maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope)

Your message dated Tue, 20 May 2014 12:34:14 + with message-id and subject line Bug#733407: fixed in maude 2.6-5 has caused the Debian Bug report #733407, regarding maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope to be marked as done. This means that you c

Bug#739312: marked as done (FTBFS with libav10)

Your message dated Tue, 20 May 2014 12:04:08 + with message-id and subject line Bug#739312: fixed in k3b 2.0.2-7.1 has caused the Debian Bug report #739312, regarding FTBFS with libav10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Processed: block 744779 with 748740

Processing commands for cont...@bugs.debian.org: > block 744779 with 748740 Bug #744779 [libwebservice-cia-perl] libwebservice-cia-perl: Fails to retrieve data from CIA factbook 744779 was not blocked by any bugs. 744779 was not blocking any bugs. Added blocking bug(s) of 744779: 748740 > thanks

Processed: Re: Bug#743141: system hangs when building gcc on kfreebsd-amd64

Processing commands for cont...@bugs.debian.org: > affects 743141 + gcc-4.6 gcc-4.7 gcc-4.8 gcc-4.9 Bug #743141 [kfreebsd-9] kfreebsd-9: triple fault on execve from 64-bit thread to 32-bit process Ignoring request to set affects of bug 743141 to the same value previously set > tags 743141 - help

Processed: Re: Bug#743141: system hangs when building gcc on kfreebsd-amd64

Processing commands for cont...@bugs.debian.org: > clone 743141 -1 -2 -3 Bug #743141 [kfreebsd-9] system hangs when building gcc on kfreebsd-amd64 Bug 743141 cloned as bugs 748743-748745 > retitle 743141 kfreebsd-9: triple fault on execve from 64-bit thread to > 32-bit process Bug #743141 [kfreeb

Bug#748742: liferea: Crashes some seconds after launch even without user interaction (segfault in libpthread)

Package: liferea Version: 1.10.8-1 Severity: grave Justification: renders package unusable Hi, the package liferea crashes predictably after 3 to 10 seconds from launch, in the dmesg i can see the problem as follows: [46072.157858] pool[8262]: segfault at 10 ip 7f80fc8fa224 sp 7f80ecb8e

Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope

I've attached 3 patches to fix FTBFS: 1) bison-parse-param.diff: this is quick and dirty patch to use %parse-param instead of deprecated YYPARSE_PARAM (and eventually removed in Bison 3.0). %parse-param was added in bison 1.875, over a decade ago, so no Build-Depends adjustments are needed. :-

Bug#743141: system hangs when building gcc on kfreebsd-amd64

tags 743141 + fixed-upstream thanks Fix committed to head: http://svnweb.freebsd.org/base?view=revision&sortby=date&revision=266464 Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? C

Processed: Re: Bug#743141: system hangs when building gcc on kfreebsd-amd64

Processing commands for cont...@bugs.debian.org: > tags 743141 + fixed-upstream Bug #743141 [kfreebsd-9] system hangs when building gcc on kfreebsd-amd64 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 743141: http://bugs.debian.org/cg

Bug#746079: marked as done (ruby-excon: FTBFS: ERROR: Test "ruby2.0" failed: no implicit conversion from nil to integer (TypeError))

Your message dated Tue, 20 May 2014 10:03:58 + with message-id and subject line Bug#746079: fixed in ruby-excon 0.33.0-1 has caused the Debian Bug report #746079, regarding ruby-excon: FTBFS: ERROR: Test "ruby2.0" failed: no implicit conversion from nil to integer (TypeError) to be marked as

Processed: waiting for the proposed update to enter wheezy proper...

Processing commands for cont...@bugs.debian.org: > found 689773 jessie/None Bug #689773 {Done: Andreas Beckmann } [elib] elib: The package elib should be rebuilt with new debhelper to get trigger support The source jessie and version None do not appear to match any binary packages Marked as found

Processed: fixed 748060 in 1.7.6-1

Processing commands for cont...@bugs.debian.org: > fixed 748060 1.7.6-1 Bug #748060 [glances] glances: python traceback on startup There is no source info for the package 'glances' at version '1.7.6-1' with architecture '' Unable to make a source version for version '1.7.6-1' Marked as fixed in v

Processed: bug 746079 is forwarded to https://github.com/geemus/excon/issues/387

Processing commands for cont...@bugs.debian.org: > forwarded 746079 https://github.com/geemus/excon/issues/387 Bug #746079 [src:ruby-excon] ruby-excon: FTBFS: ERROR: Test "ruby2.0" failed: no implicit conversion from nil to integer (TypeError) Bug #747737 [src:ruby-excon] FTBFS: no implicit conve

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

Hi, Matthias Klose writes: > I'm not complaing about the name of the package, but that it apparently *does* > have some unintended effects on some architectures. is there something simpler than gcc that FTBFS? I'd like to look into the issue but gcc is quite heavy to build, especially on a porte

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

Am 20.05.2014 10:57, schrieb Mark Wielaard: > I am just not clear what the precise bugs are that you are seeing. The > gcc example is somewhat hard to understand. Is the issue you are seeing > with gcc really caused by sys/sdt.h or might it be the g++ template decl > ordering problem discussed here

Bug#748694: sys/sdt.h is architecture specific, and causing issues on unsupported architectures

On Mon, 2014-05-19 at 22:53 +0200, Matthias Klose wrote: > Am 19.05.2014 21:00, schrieb Mark Wielaard: > > It is just the package name > > that refers to systemtap, but it could as well have been called > > gdb-sdt-devel for example. In which case it should at least work as is > > on any arch gdb

Bug#733407: maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope

Hi, I have to admit that I do not have any idea about bison and thus fail to fix bug #733407. Any help is really appreciated. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Co

Processed: Tagging help

Processing commands for cont...@bugs.debian.org: > tags 733407 help Bug #733407 [src:maude] maude: FTBFS: surface.yy:63:67: error: 'parseResult' was not declared in this scope Added tag(s) help. > thanks Stopping processing here. Please contact me if you need assistance. -- 733407: http://bugs.

Bug#748574: 3.14.1 does not boot on Dell server

Package: src:linux Version: 3.14.4-1 Followup-For: Bug #748574 Dear Maintainer, Is this related to the problem reported on Arch Linux https://bugs.archlinux.org/task/39811 which seems to have been reported to the kernel people :- https://bugzilla.kernel.org/show_bug.cgi?id=73911#c8 I had this