Bug#767892: subtitleeditor: Cannot type or edit subtitles

Hi, I uploaded the fixed version to m.d.n: http://mentors.debian.net/package/subtitleeditor I'll bother my sponsor now ;) Best, Philip signature.asc Description: Digital signature

Processed: Re: [Pkg-sysvinit-devel] Bug#601757: Please mount cgroup automatically

Processing control commands: > severity -1 wishlist Bug #601757 [initscripts] Please mount cgroup automatically Bug #748291 [initscripts] Please mount cgroup automatically Bug #768919 [initscripts] Please mount cgroup automatically Severity set to 'wishlist' from 'grave' Severity set to 'wishlist'

Bug#601757: [Pkg-sysvinit-devel] Bug#601757: Please mount cgroup automatically

Control: severity -1 wishlist Control: forcemerge 572733 -1 On 11/11/2014 12:54 PM, Petter Reinholdtsen wrote: > [Ritesh Raj Sarraf] >> The bug is more than 4 years old. And no maintainer wants to bring >> it to closure. There's no comment even whether it is something >> correct or not. > > I be

Bug#601757: [Pkg-sysvinit-devel] Bug#601757: Please mount cgroup automatically

[Ritesh Raj Sarraf] > The bug is more than 4 years old. And no maintainer wants to bring > it to closure. There's no comment even whether it is something > correct or not. I believe cgroup was discussed in http://bugs.debian.org/572733 > already. Is there something new since that bug report? --

Bug#601757: Please mount cgroup automatically

On 11/11/2014 03:54 AM, John Paul Adrian Glaubitz wrote: > Hello Ritesh! > > May I ask why you set the severity to "grave"? As far as I know, > Debian Jessie is going to be released with systemd as the default > init for all release architectures to which kfreebsd-* does not > belong to. > The b

Bug#760377: confirm apache 1 and gpl-1+ situation

* Paul Gevers: > [2] > http://anonscm.debian.org/cgit/collab-maint/xmlrpc-c.git/tree/lib/util/getoptx.h?h=debian-sid You should investigate if you can use the getopt from glibc, which is released under the LGPL. > [3] > http://anonscm.debian.org/cgit/collab-maint/xmlrpc-c.git/tree/tools/turbocha

Processed: tagging 768926

Processing commands for cont...@bugs.debian.org: > tags 768926 + pending Bug #768926 [qemu-user-static] qemu-user-static provides static executables but does not have Built-Using field Ignoring request to alter tags of bug #768926 to the same tags previously set > thanks Stopping processing here.

Bug#768911: [pkg-cli-apps-team] Bug#768911: Bug#768911: Bug#768911: gnome-do: desktop freezes when gnome-do is launched

Ok. I can now reproduce this too, but *only* if Do is set to show on startup (which I didn't have). I wonder if this is related to the GMutex unpleasantness recently. I'll investigate. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Troubl

Bug#768769: plastimatch: FTBFS in jessie: Tests failures

Hi Gregory, On Mon, Nov 10, 2014 at 12:01:48PM -0800, Gregory Sharp wrote: > This is a bug in upstream, where the regression test > is missing a dependency. I'm not sure what this really means but if it is a missing dependency do you want to express that we can fix this by just another Build-Depe

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

On Mon, Nov 10, 2014 at 06:05:36PM -0500, Yaroslav Halchenko wrote: > > On Mon, 10 Nov 2014, Andreas Tille wrote: > > > On Mon, Nov 10, 2014 at 12:51:39PM -0500, Yaroslav Halchenko wrote: > > > amount of changes from 0.8.4 to 0.8.6 seems to be miniscule and just a > > > bug fix so we could demand

Bug#768903: marked as done (subversion: FTBFS in parallel mode: dh_install: libsvn_delta exists in debian/tmp but is not installed to anywhere)

Your message dated Tue, 11 Nov 2014 05:34:06 + with message-id and subject line Bug#768903: fixed in subversion 1.8.10-4 has caused the Debian Bug report #768903, regarding subversion: FTBFS in parallel mode: dh_install: libsvn_delta exists in debian/tmp but is not installed to anywhere to be

Bug#767445: (no subject)

Hello, I have already sent a RFS for requests 2.4.3-3 with a fix for this. I already tried python-docker 0.5.3-1 after building it inside a pbuilder chroot: using requests 2.4.3-3, python-docker works. See this thread for details: https://lists.debian.org/debian-python/2014/11/msg1.html Spe

Processed: tagging 767826

Processing commands for cont...@bugs.debian.org: > tag 767826 +patch Bug #767826 [python3-django-assets] python3-django-assets: fails to install: SyntaxError: Missing parentheses in call to 'print' Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -

Bug#767826: python3-django-assets: fails to install: SyntaxError: Missing parentheses in call to 'print'

Hello, I have noticed this error when installing this package. Attached is a trivial patch that fixes this bug Sent upstream: https://github.com/miracle2k/django-assets/pull/47 -- Jason Pleau Description: python3 compat for pytest_plugin.py Trivial change to make the print statement compatibl

Bug#768686: maxima ftbfs due to gcl dependency

Hi Camm, It looks like you're gcl uploads didn't make it to testing in time for the freeze, but maxima did. Maxima in testing now has an unsatisfiable build dependency on gcl in unstable. I did a rebuild of maxima 5.34.1-2 with gcl 2.6.11-3 from testing, which seemed to work just fine, but I'm n

Bug#766114: [pkg-fso-maint] Bug#766114: Aw: Re: Bug#766114: Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf

Hi, Sorry for the long time to answer, but I had no time to dig into this. On Thu, Nov 06, 2014 at 10:40:39PM +0100, hikaru.deb...@web.de wrote: > > Hmm, it's a strange thing. If I recompile fso-deviced eveything works as > > expected. > > But you can reproduce the problem with the packages as

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tag 769047 + pending Bug #769047 [src:requests] requests.packages.urllib3 stub must be the same of global urllib3 package Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 769047: http://bugs.

Bug#768937: [Pkg-zsh-devel] Bug#768937: zsh: [patch] not binNMU-safe due to --link-doc between arch-dep and arch-indep

Control: tag -1 - patch pending Hi Simon, I'm not yet sure what's the culprit, but after applying your patch (without the changelog) to the current HEAD of our packging git repo, the installation of zsh-common always aborts as follows: Preparing to unpack zsh-common_5.0.7-4_all.deb ... Unpacking

Processed: Re: [Pkg-zsh-devel] Bug#768937: zsh: [patch] not binNMU-safe due to --link-doc between arch-dep and arch-indep

Processing control commands: > tag -1 - patch pending Bug #768937 [zsh] zsh: [patch] not binNMU-safe due to --link-doc between arch-dep and arch-indep Removed tag(s) pending and patch. -- 768937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768937 Debian Bug Tracking System Contact ow...@bu

Bug#768841: libgnutls-deb0-28: SIGABRT when loading certificates

Coin, Quoting Andreas Metzler : Could you check whether upgrading to 3.3.10 (just uploaded to experimental) fixes the issues you reported, too? You're right, this fixed the problem for both minbif and ircd-ratbox. PS: Looking at thi

Processed: tagging 768937

Processing commands for cont...@bugs.debian.org: > tags 768937 + pending Bug #768937 [zsh] zsh: [patch] not binNMU-safe due to --link-doc between arch-dep and arch-indep Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 768937: http://bugs.deb

Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'

Well, it's not really a "why not" decision :) , I mean, it's somehow a kind of commitment statement. I mean, while debian/changelog essentially talks about the past (who did what), imo Maintaner and Uploaders talk about the future of the packahe, more or less saying: "hey, if there's something to f

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 765120 important Bug #765120 [src:monogame] monogame: FTBFS: unsatisfiable build-dependency: monodevelop (< 4.0.12.) but 5.5.0.227-1 is to be installed Severity set to 'important' from 'serious' > retitle 765120 monogame: support monodev

Bug#754688: marked as done (kwave: FTBFS on kfreebsd-*: collect2: error: ld returned 1 exit status)

Your message dated Tue, 11 Nov 2014 00:06:38 + with message-id <2014000638.gb13...@squeeze.pyro.eu.org> and subject line Re: Bug#754688: kwave: FTBFS on kfreebsd-*: collect2: error: ld returned 1 exit status has caused the Debian Bug report #754688, regarding kwave: FTBFS on kfreebsd-*: co

Bug#769047: requests.packages.urllib3 stub must be the same of global urllib3 package

Source: requests Version: 2.4.3-1 Severity: critical Justification: breaks unrelated software To prevent other bugs like #767445. Look at the whole thread for a complete explanation: https://lists.debian.org/debian-python/2014/11/msg1.html -- System Information: Debian Release: jessie/sid

Bug#743057: FTBFS, testsuite failure

Hello buzztard has gone from Debian, see https://tracker.debian.org/pkg/buzztard buzztard has been removed from testing on 2013-12-31 (https://tracker.debian.org/news/435659) buzztard has been removed from unstable on 2014-05-20 (https://tracker.debian.org/news/435660) So I think that this bug c

Processed: tagging 769011

Processing commands for cont...@bugs.debian.org: > tags 769011 + jessie Bug #769011 [src:python-stem] src:python-stem: maintainer address bounces Added tag(s) jessie. > thanks Stopping processing here. Please contact me if you need assistance. -- 769011: http://bugs.debian.org/cgi-bin/bugreport.

Bug#720378: cctools: FTBFS on non-linux

Hello I wanted to test this bug, but cctools is no more in Debian. Bug was opened on 2013/08/21 cctools was removed from Debian on 2013/09/08 See https://tracker.debian.org/news/153893 So I think this bug could be marked as fixed. Best regards Gianluca Bonetti -- To UNSUBSCRIBE, email to de

Processed: Re: A new RC

Processing control commands: > severity -1 serious Bug #768570 [ckeditor] ckeditor: missing core/_bootstrap.js Severity set to 'serious' from 'important' > tags -1 + pending Bug #768570 [ckeditor] ckeditor: missing core/_bootstrap.js Added tag(s) pending. -- 768570: http://bugs.debian.org/cgi-bi

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

On Mon, 10 Nov 2014, Andreas Tille wrote: > On Mon, Nov 10, 2014 at 12:51:39PM -0500, Yaroslav Halchenko wrote: > > amount of changes from 0.8.4 to 0.8.6 seems to be miniscule and just a > > bug fix so we could demand unblock for this one > I'll take the bet that this will fail. I personally wo

Bug#759960: libcatalyst-engine-psgi-perl: FTBFS: dh_auto_test: make -j1 test returned exit code 2

On Sun, 09 Nov 2014 18:45:25 +, Simon McVittie wrote: > On Sat, 25 Oct 2014 at 20:04:19 +0200, gregor herrmann wrote: > > libmojomojo-perl uploaded with the patch and without the dependency > > on libcatalyst-engine-psgi-perl, so the latter can be removed from > > testing (and the archive). >

Bug#766994: marked as done (systemtap-mode.el:62:1:Error: Symbol's function definition is void: cl-macroexpand-all)

Your message dated Mon, 10 Nov 2014 22:49:13 + with message-id and subject line Bug#766994: fixed in systemtap 2.6-0.2 has caused the Debian Bug report #766994, regarding systemtap-mode.el:62:1:Error: Symbol's function definition is void: cl-macroexpand-all to be marked as done. This means t

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

On Mon, Nov 10, 2014 at 12:51:39PM -0500, Yaroslav Halchenko wrote: > amount of changes from 0.8.4 to 0.8.6 seems to be miniscule and just a > bug fix so we could demand unblock for this one I'll take the bet that this will fail. I personally would not try to stress test the patience of the relea

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

On Mon, Nov 10, 2014 at 05:48:32PM +0100, Alexandre Gramfort wrote: > hi, > > ok but the current master branch on debian.org is at version 0.8.6. > > I doubt I should make changes their for version 0.8.4 no? Just create a branch named jessie starting from 0.8.4. Unfortunately your sponsor has i

Bug#601757: Please mount cgroup automatically

Hello Ritesh! May I ask why you set the severity to "grave"? As far as I know, Debian Jessie is going to be released with systemd as the default init for all release architectures to which kfreebsd-* does not belong to. I don't think that this bug is going to be fixed any time soon if the sysvini

Bug#741834: patch to add LC_ALL=C

tag 741834 +patch thank you Hi, this is a tiny patch to address the test failures. Thank you Thomas diff -Nru python-babel-1.3+dfsg.1/debian/changelog python-babel-1.3+dfsg.1/debian/changelog --- python-babel-1.3+dfsg.1/debian/changelog 2014-06-24 09:06:24.0 +0200 +++ python-babel-1.3

Processed: your mail

Processing commands for cont...@bugs.debian.org: > retitle 749365 lucene2: FTBFS - sporadic test failure Bug #749365 [lucene2] lucene2: FTBFS - tests fail Changed Bug title to 'lucene2: FTBFS - sporadic test failure' from 'lucene2: FTBFS - tests fail' > severity 749365 important Bug #749365 [luce

Processed: patch to add LC_ALL=C

Processing commands for cont...@bugs.debian.org: > tag 741834 +patch Bug #741834 [src:python-babel] python-babel: FTBFS: Tests failures Added tag(s) patch. > thank you Stopping processing here. Please contact me if you need assistance. -- 741834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Processed: tagging moreinfo

Processing commands for cont...@bugs.debian.org: > tags 768905 + moreinfo Bug #768905 [src:keyutils] FTBFS: fails test "CHECK INVALID KEY TYPE" Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 768905: http://bugs.debian.org/cgi-bin/bugreport.

Bug#749365: lucene2: FTBFS - tests fail

I rebuilt lucene2 ten times with pbuilder. It succeeded 9 times and failed once but with a different test failure (also reported by Miguel on debian-java in July): [junit] Testcase: testPhraseQueryWithStopAnalyzer(org.apache.lucene.search.TestPhraseQuery): FAILED [junit] expected:<1

Bug#768785: marked as done (eagle: switch from libjpeg62-dev to libjpeg-dev)

Your message dated Mon, 10 Nov 2014 21:34:31 + with message-id and subject line Bug#768785: fixed in eagle 6.6.0-2 has caused the Debian Bug report #768785, regarding eagle: switch from libjpeg62-dev to libjpeg-dev to be marked as done. This means that you claim that the problem has been deal

Bug#760377: WIP: possible debdiff

Just so it is tracked in case somebody else looks into this before I finish, find my current work and proposal attached. Paul diff --git a/debian/changelog b/debian/changelog index 57b48db..1abf0cf 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,13 @@ +xmlrpc-c (1.33.14-0.2) unstab

Bug#760377: confirm apache 1 and gpl-1+ situation

Hi Debian Legal readers [Please keep the bug in CC to document the discussion there.] I am investigating the situation of xmlrpc-c because of RC bug 760377 [1]. The point is that a statement about a GPL-1+ file [2] was missing in the d/copyright file. While checking the package for other missing s

Processed: tagging 767659

Processing commands for cont...@bugs.debian.org: > tags 767659 - patch pending Bug #767659 [libpoppler-glib8] evince 3.14.1-1 gets undefined symbol with libpoppler46:i386 earlier than 0.26.5-2 Bug #768475 [libpoppler-glib8] evince: segfault on trying to open a pdf Bug #768985 [libpoppler-glib8] l

Processed: tagging 768876

Processing commands for cont...@bugs.debian.org: > tags 768876 + pending Bug #768876 [busybox] busybox-static is statically linked against libc6, but doesn't have a Built-Using: field Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 768876: h

Bug#767659: poppler: diff for NMU version 0.26.5-2.1

On 10/11/14 20:44, Pino Toscano wrote: > Please drop this NMU, since the approach chosen (bumping shlibs for > everybody) is not correct. Cancelled, sorry about that. I hadn't realised so many things link to that library directly (as opposed to via poppler-glib and friends). S -- To UNSUBS

Bug#767659: poppler: diff for NMU version 0.26.5-2.1

On 2014-11-10 21:36, Simon McVittie wrote: Control: tags 767659 + patch Control: tags 767659 + pending Dear maintainer, I've prepared an NMU for poppler (versioned as 0.26.5-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Please drop this NMU, since

Bug#767659: poppler: diff for NMU version 0.26.5-2.1

Control: tags 767659 + patch Control: tags 767659 + pending Dear maintainer, I've prepared an NMU for poppler (versioned as 0.26.5-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards, S diffstat for poppler-0.26.5 poppler-0.26.5 changelog |

Processed: poppler: diff for NMU version 0.26.5-2.1

Processing control commands: > tags 767659 + patch Bug #767659 [libpoppler-glib8] evince 3.14.1-1 gets undefined symbol with libpoppler46:i386 earlier than 0.26.5-2 Bug #768475 [libpoppler-glib8] evince: segfault on trying to open a pdf Bug #768985 [libpoppler-glib8] libpoppler-glib.so.8: undefin

Processed: steps to reproduce

Processing control commands: > tags -1 -unreproducible Bug #766994 [systemtap-common] systemtap-mode.el:62:1:Error: Symbol's function definition is void: cl-macroexpand-all Removed tag(s) unreproducible. > tags -1 -moreinfo Bug #766994 [systemtap-common] systemtap-mode.el:62:1:Error: Symbol's fun

Processed: not affecting jessie

Processing commands for cont...@bugs.debian.org: > notfound 758600 2.5.3+dfsg-1 Bug #758600 [shibboleth-sp2-utils] shibboleth-sp2-utils: postinst fails on initial installation Ignoring request to alter found versions of bug #758600 to the same values previously set > thanks Stopping processing h

Bug#768769: plastimatch: FTBFS in jessie: Tests failures

Thank you for the report. This is a bug in upstream, where the regression test is missing a dependency. -- Greg Sharp gregsh...@geocities.com - Original Message - > From: Lucas Nussbaum > To: sub...@bugs.debian.org > Cc: > Sent: Sunday, November 9, 2014 2:26 AM > Subject: Bug#768

Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'

On Mon, Nov 10, 2014 at 08:07:21PM +0100, Miriam Ruiz wrote: > Thanks a lot, I'll have a look at it and commit it.Do you want to be > included in Uploaders, as the patch seems to say? If you do, you're > essentially declaring that you're willing to take care of that > package, essentially :) Sure,

Processed: notfound 769023 in 1.0.1j-1, found 769023 in 1.0.2~beta3-1, tagging 769023

Processing commands for cont...@bugs.debian.org: > notfound 769023 1.0.1j-1 Bug #769023 [libssl1.0.0] libssl1.0.0 from experimental renders the following packages unusable: reportbug, namebench. Ignoring request to alter found versions of bug #769023 to the same values previously set > found 769

Processed: Re: Bug#769023: libssl1.0.0 from experimental renders the following packages unusable: reportbug, namebench.

Processing commands for cont...@bugs.debian.org: > found 769023 1.0.2~beta3-1 Bug #769023 [libssl1.0.0] libssl1.0.0 from experimental renders the following packages unusable: reportbug, namebench. Marked as found in versions openssl/1.0.2~beta3-1. > notfound 769023 1.0.1j-1 Bug #769023 [libssl1.0

Bug#758600: shibboleth-sp2-utils: postinst fails on initial installation

On Monday 10 November 2014 09:06:34 Russ wrote: > I'll try to take a look, but I no longer use Shibboleth and handed the > package maintenance off. Copying the general mailing list. Sorry then, I CC'd you explicitly as you did the backport, with additional changes over the plain jessie package,

Bug#769023: libssl1.0.0 from experimental renders the following packages unusable: reportbug, namebench.

Package: libssl1.0.0 Version: 1.0.1j-1 Severity: critical Tags: upstream Justification: breaks unrelated software I could reproduce this on 2 machines I run. My base System ist jessie. Solution: downgrade libssl1.0.0 and openssl to the versions in jessie. -- System Information: Debian Releas

Bug#768741: phlipple: FTBFS in jessie: ld: engine.o: undefined reference to symbol 'cos@@GLIBC_2.2.5'

Thanks a lot, I'll have a look at it and commit it.Do you want to be included in Uploaders, as the patch seems to say? If you do, you're essentially declaring that you're willing to take care of that package, essentially :) Greetings, Miry 2014-11-10 10:50 GMT+01:00 Peter Pentchev : > package src

Bug#768841: libgnutls-deb0-28: SIGABRT when loading certificates

Control: severity -1 serious On 2014-11-09 "Marc Dequènes (Duck)" wrote: > Package: libgnutls-deb0-28 > Version: 3.3.8-3 > Severity: grave > Justification: breaks related softwares (minbif, ircd-ratbox) > Control: affects -1 = minbif ircd-ratbox [...] > Reverting the certificates (which are stil

Processed: Re: Bug#768841: libgnutls-deb0-28: SIGABRT when loading certificates

Processing control commands: > severity -1 serious Bug #768841 [libgnutls-deb0-28] libgnutls-deb0-28: SIGABRT when loading certificates Severity set to 'serious' from 'grave' -- 768841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768841 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#760476: gnutls28 3.3.8-3

On 2014-10-22 Christophe Ségui wrote: > Here is the trace of cups in start phase. Hello Christophe, could you check whether gnutls 3.3.10-1 fixes the issue for you? I have just uploaded this version to experimental, it should hit the mirrors in a couple of hours. cu Andreas -- `What a good fr

Processed: tagging 758600

Processing commands for cont...@bugs.debian.org: > tags 758600 + wheezy Bug #758600 [shibboleth-sp2-utils] shibboleth-sp2-utils: postinst fails on initial installation Added tag(s) wheezy. > thanks Stopping processing here. Please contact me if you need assistance. -- 758600: http://bugs.debian

Bug#769011: Ulises Vitulli Bouncing

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: der...@madap.com.ar Unrouteable address This is a serious bug in your packages that could cause them to be removed and not re-instated (since we are

Bug#766492: libecap: FTBFS: Makefile.am: error: required file './NEWS' not found

Hi Andrey, Thanks a lot for you patch. I’ve added it and uploaded 0.2.0-3 right now. I’ll push the patch upstream but since it has already moved to 1.0.0 with different autoconf script I don’t see the chance for it to be applied. Regards, L -- Luigi Gangitano -- -- GPG: 1024D/924C0C26: 12F8

Bug#768996: marked as done (nas: FTBFS on arm64/ppc64el)

Your message dated Mon, 10 Nov 2014 18:34:20 + with message-id and subject line Bug#768996: fixed in nas 1.9.4-3 has caused the Debian Bug report #768996, regarding nas: FTBFS on arm64/ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#758600: shibboleth-sp2-utils: postinst fails on initial installation

I'd like to better understand the severity issue. Are you saying that there's no order I can install shibboleth and apache in wheezy that will work? I.E. even if I manually install the module first? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscrib

Bug#766492: marked as done (libecap: FTBFS: Makefile.am: error: required file './NEWS' not found)

Your message dated Mon, 10 Nov 2014 18:34:08 + with message-id and subject line Bug#766492: fixed in libecap 0.2.0-3 has caused the Debian Bug report #766492, regarding libecap: FTBFS: Makefile.am: error: required file './NEWS' not found to be marked as done. This means that you claim that th

Processed: Re: [Openjdk] Bug#766601: openjdk-7-jre-headless: still depending on libjpeg8?

Processing control commands: > severity -1 serious Bug #766601 [openjdk-7-jre-headless] openjdk-7-jre-headless: still depending on libjpeg8? Severity set to 'serious' from 'minor' -- 766601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766601 Debian Bug Tracking System Contact ow...@bugs.de

Processed: Re: Bug#768703: chemfp: FTBFS in jessie: build-dependency not installable: python-unit

Processing control commands: > tags -1 + patch Bug #768703 [src:chemfp] chemfp: FTBFS in jessie: build-dependency not installable: python-unit Added tag(s) patch. -- 768703: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768703 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#768703: chemfp: FTBFS in jessie: build-dependency not installable: python-unit

Control: tags -1 + patch On Sun, Nov 09, 2014 at 08:36:41PM +0500, Andrey Rahmatullin wrote: > On Sun, Nov 09, 2014 at 08:40:58AM +0100, Lucas Nussbaum wrote: > > > sbuild-build-depends-chemfp-dummy : Depends: python-unit but it is not > > > installable > python-unit was removed from testing on

Bug#769011: src:python-stem: maintainer address bounces

Source: python-stem Version: 1.2.2-1 Severity: serious Tags: sid X-Debbugs-Cc: Scott Kitterman [ CC'ed last uploader. ] Hi, the maintainer address for python-stem bounces, see below. Ansgar Mail Delivery System writes: > This message was created automatically by mail delivery software. > > A

Bug#768696: libsecret: FTBFS in jessie: tests timeout

Control: tags -1 unreproducible Control: severity -1 important On 09/11/14 08:16, Lucas Nussbaum wrote: > Source: libsecret > Version: 0.18-1 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20141108 qa-ftbfs > Justification: FTBFS in jessie on amd64 >

Processed: Re: Bug#768696: libsecret: FTBFS in jessie: tests timeout

Processing control commands: > tags -1 unreproducible Bug #768696 [src:libsecret] libsecret: FTBFS in jessie: tests timeout Added tag(s) unreproducible. > severity -1 important Bug #768696 [src:libsecret] libsecret: FTBFS in jessie: tests timeout Severity set to 'important' from 'serious' -- 768

Processed: Re: Bug#767892: subtitleeditor: Cannot type or edit subtitles

Processing commands for cont...@bugs.debian.org: > severity 767892 grave Bug #767892 [subtitleeditor] subtitleeditor: Cannot type or edit subtitles Severity set to 'grave' from 'important' > tags 767892 + pending Bug #767892 [subtitleeditor] subtitleeditor: Cannot type or edit subtitles Added tag(

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

amount of changes from 0.8.4 to 0.8.6 seems to be miniscule and just a bug fix so we could demand unblock for this one $> git diff v0.8.4..v0.8.6 --stat MANIFEST.in | 5 + doc/source/whats_new.rst | 2 +- mne/__init__.py | 2 +- mne/coreg.py | 3 ++- so I thi

Bug#769002: scilab: FTBFS on arm64, ppc64el, s390x

Hello, 2014-11-10 18:15 GMT+01:00 Sylvestre Ledru : > This is caused by the fact that libjogl2-java has been be built on these > archs: > https://buildd.debian.org/status/package.php?p=libjogl2-java Note there is another report for that, #769003. Maybe you want to block this bug on #769003? Reg

Bug#768699: marked as done (apparmor-profiles-extra: FTBFS in jessie: Tests failures)

Your message dated Mon, 10 Nov 2014 18:26:35 +0100 with message-id <20141110172635.gb19...@xanadu.blop.info> and subject line Re: Bug#768699: apparmor-profiles-extra: FTBFS in jessie: Tests failures has caused the Debian Bug report #768699, regarding apparmor-profiles-extra: FTBFS in jessie: Tests

Bug#768519: nautilus does not start from dash when it handles the desktop

Package: nautilus Version: 3.14.0-1 Followup-For: Bug #768519 Only occurs when "..handle desktop" in gnome-tweak is enabled. See attached videos. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture:

Bug#769002: scilab: FTBFS on arm64, ppc64el, s390x

On 10/11/2014 18:00, Hector Oron wrote: > Source: scilab > Version: 5.5.1-3 > Severity: serious > Justification: FTBFS > > > > *** /home/zumbi/bin/ftbfs-armel > Hello, > > Your package fails to build from source on Debian autobuilder network. > > Please check your package build logs at: >

Processed: severity of 768995 is serious

Processing commands for cont...@bugs.debian.org: > severity 768995 serious Bug #768995 [dateutils] dateutils: please do not use -march=native Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 768995: http://bugs.debian.org/

Bug#758600: shibboleth-sp2-utils: postinst fails on initial installation

Luca Bruno writes: > I'm raising the severity of this, since the backported package is > currently unusable in this case, due to the hard-coupled implicit > dependency on Apache. > Russ, can you please revert/modify your a2enmod changes for the ~bpo > revision? I'll try to take a look, but I no

Bug#769004: sphinxsearch: FTBFS on all arches

Source: sphinxsearch Version: 2.2.5-1 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: Full log: https

Bug#769003: libjogl2-java: FTBFS on arm64, ppc64el, s390x

Source: libjogl2-java Version: 2.2.4+dfsg-1 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: arm64 ful

Bug#769002: scilab: FTBFS on arm64, ppc64el, s390x

Source: scilab Version: 5.5.1-3 Severity: serious Justification: FTBFS *** /home/zumbi/bin/ftbfs-armel Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at:

Bug#768999: aces3: FTBFS on arm64

severity 768999 important tags 768999 +help thanks On Mon, Nov 10, 2014 at 05:46:26PM +0100, Hector Oron wrote: > Source: aces3 > Version: 3.0.8-4 > Severity: serious > Justification: FTBFS Well, aces3_3.0.8 was never built on arm64, so I don't consider this to be an RC bug. > Your package f

Processed: Re: Bug#768999: aces3: FTBFS on arm64

Processing commands for cont...@bugs.debian.org: > severity 768999 important Bug #768999 [src:aces3] aces3: FTBFS on arm64 Severity set to 'important' from 'serious' > tags 768999 +help Bug #768999 [src:aces3] aces3: FTBFS on arm64 Added tag(s) help. > thanks Stopping processing here. Please cont

Bug#768730: [Debian-med-packaging] Bug#768730: [lu...@lucas-nussbaum.net: Bug#768730: python-mne: FTBFS in jessie: Tests failures]

hi, ok but the current master branch on debian.org is at version 0.8.6. I doubt I should make changes their for version 0.8.4 no? these 3 tests > test_legendre_val > test_legendre_table > test_make_field_map_meg should be deleted by the patch. Alex On Mon, Nov 10, 2014 at 2:30 PM, Andreas Ti

Bug#769001: python-magcode-core: FTBFS on all arches

Source: python-magcode-core Version: 1.4.7-1 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: de

Bug#768750: marked as done (oce: FTBFS in jessie: glxext.h:480:143: error: 'GLintptr' has not been declared)

Your message dated Mon, 10 Nov 2014 16:50:34 + with message-id and subject line Bug#768750: fixed in oce 0.15-5 has caused the Debian Bug report #768750, regarding oce: FTBFS in jessie: glxext.h:480:143: error: 'GLintptr' has not been declared to be marked as done. This means that you claim

Bug#768999: aces3: FTBFS on arm64

Source: aces3 Version: 3.0.8-4 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: Full log at: https://buildd.d

Processed: Re: love-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc/love/demos/lovalanche.love

Processing control commands: > tags -1 + patch Bug #768206 [love-doc] love-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc/love/demos/lovalanche.love Added tag(s) patch. -- 768206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768206 Debian Bug Tracking System Contac

Bug#768206: love-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc/love/demos/lovalanche.love

Control: tags -1 + patch Hi, This seems to be caused by moving files between packages without adding the needed Breaks and Replaces. I made a patch (svn diff) for the package with the help of Debian wiki page[1]. [1] https://wiki.debian.org/PackageTransition (please see case #9) Cheers, Juhan

Bug#768998: kadu-mime-tex: FTBFS on all arches

Source: kadu-mime-tex Version: 1.0-2 Severity: serious Justification: FTBFS *** /home/zumbi/bin/ftbfs-armel Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at:

Bug#768996: nas: FTBFS on arm64/ppc64el

Source: nas Version: 1.9.4-2 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: You'll probably want to update config

Processed: merge 768985 767659 768475

Processing commands for cont...@bugs.debian.org: > reassign 768985 libpoppler-glib8 0.26.5-2 Bug #768985 [evince] libpoppler-glib.so.8: undefined symbol Segmentation fault Bug reassigned from package 'evince' to 'libpoppler-glib8'. No longer marked as found in versions evince/3.14.1-1. Ignoring re

Bug#768685: libtheora: FTBFS in jessie: ld: player_example-player_example.o: undefined reference to symbol 'rintf@@GLIBC_2.2.5'

tags 768685 + patch pending thanks Hi Simon! Thanks for your help! The patch works fine. It compiles in my unstable jail on amd64 and the player example binary still works as expected. Cheers, Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "un

Processed: Re: Bug#768685: libtheora: FTBFS in jessie: ld: player_example-player_example.o: undefined reference to symbol 'rintf@@GLIBC_2.2.5'

Processing commands for cont...@bugs.debian.org: > tags 768685 + patch pending Bug #768685 [src:libtheora] libtheora: FTBFS in jessie: ld: player_example-player_example.o: undefined reference to symbol 'rintf@@GLIBC_2.2.5' Added tag(s) pending and patch. > thanks Stopping processing here. Pleas

Bug#768800: marked as done (libaudio2: not multiarch-binNMU safe)

Your message dated Mon, 10 Nov 2014 16:21:18 + with message-id and subject line Bug#768651: fixed in nas 1.9.4-2 has caused the Debian Bug report #768651, regarding libaudio2: not multiarch-binNMU safe to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#768651: marked as done (libaudio2: fails to update - trying to overwrite shared '/usr/share/doc/libaudio2/changelog.Debian.gz')

Your message dated Mon, 10 Nov 2014 16:21:18 + with message-id and subject line Bug#768651: fixed in nas 1.9.4-2 has caused the Debian Bug report #768651, regarding libaudio2: fails to update - trying to overwrite shared '/usr/share/doc/libaudio2/changelog.Debian.gz' to be marked as done. Th

Bug#767555: marked as done (python-stem,python3-stem: error when trying to install together)

Your message dated Mon, 10 Nov 2014 16:21:36 + with message-id and subject line Bug#767555: fixed in python-stem 1.2.2-1.1 has caused the Debian Bug report #767555, regarding python-stem,python3-stem: error when trying to install together to be marked as done. This means that you claim that t

  1   2   3   >