Bug#801106: marked as done (sddm-greeter fails to start)

Your message dated Wed, 30 Dec 2015 01:01:20 -0500 with message-id <2091693.GgmntflHtQ@kitterma-e6430> and subject line Re: Bug#801106: sddm-greeter fails to start has caused the Debian Bug report #801106, regarding sddm-greeter fails to start to be marked as done. This means that you claim that t

Processed: forcibly merging 809198 780103

Processing commands for cont...@bugs.debian.org: > forcemerge 809198 780103 Bug #809198 [maildirsync] maildirsync broken with perl 5.22 Bug #780103 [maildirsync] maildirsync: please re-enable maildirsync.pl.diff patch Severity set to 'grave' from 'normal' 796345 was blocked by: 787450 808209 8046

Bug#805123: marked as done (swi-prolog: FTBFS on ppc64el)

Your message dated Wed, 30 Dec 2015 03:36:31 + with message-id and subject line Bug#805123: fixed in swi-prolog 7.2.0-3 has caused the Debian Bug report #805123, regarding swi-prolog: FTBFS on ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#804888: djview plugin unusable in debian testing...

Rethreading to l...@bottou.org On 12/29/15, 6:28 PM, "Leon Bottou" wrote: >I've already reported a bug against qt5 for this with a little test case. > > > >And also a bug upstream referencing the debian bug... > >- L. > > > > > >On

Bug#809291: marked as done (sleekxmpp: FTBFS: ImportError: No module named thirdparty.statemachine)

Your message dated Tue, 29 Dec 2015 23:42:54 + with message-id and subject line Bug#809291: fixed in sleekxmpp 1.3.1-3 has caused the Debian Bug report #809291, regarding sleekxmpp: FTBFS: ImportError: No module named thirdparty.statemachine to be marked as done. This means that you claim tha

Bug#799841: marked as done (Beta release of saods9 entered unstable)

Your message dated Tue, 29 Dec 2015 23:42:46 + with message-id and subject line Bug#799841: fixed in saods9 7.4+repack-1 has caused the Debian Bug report #799841, regarding Beta release of saods9 entered unstable to be marked as done. This means that you claim that the problem has been dealt

Bug#804888: djview plugin unusable in debian testing...

I've already reported a bug against qt5 for this with a little test case. And also a bug upstream referencing the debian bug... - L. On 12/29/15, 5:12 PM, "Barak A. Pearlmutter" wrote: >So maybe the best thing would be to file a b

Bug#804888: djview plugin unusable in debian testing...

So maybe the best thing would be to file a bug against qt5, fix things in this package by using qt4, and filing a wishlist bug against this package to use qt5, with a "blocked by" referring to the qt5 bug report above. That way when the qt5 issue is resolved the wishlist bug will be unblocked and n

Processed: Re: mu-cade: ODE INTERNAL ERROR 1: assertion "bNormalizationResult" failed in _dNormalize4

Processing commands for cont...@bugs.debian.org: > tags 809369 stretch sid Bug #809369 [mu-cade] mu-cade: ODE INTERNAL ERROR 1: assertion "bNormalizationResult" failed in _dNormalize4 Added tag(s) sid and stretch. > thanks Stopping processing here. Please contact me if you need assistance. -- 8

Bug#809359: long-term redmine debian packaging

Hi! ["out of date redmine" bug report in CC. this is a followup email to the generic "we're going to LTS redmine!" notification which expands on the situation and hopefully the future of the Redmine packaging] I am trying to figure out how to maintain Redmine in the long term, especially in the o

Bug#804888: djview plugin unusable in debian testing...

The upstream code for djview has been improved. However the core of this problem is bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809367 in Stretch's Qt-5.5.1. Absent a Qt fix, we have two ugly workarounds: * Compiling djview4 using Qt-4.8 instead of Qt-5. * Have djview4 recogni

Bug#809369: mu-cade: ODE INTERNAL ERROR 1: assertion "bNormalizationResult" failed in _dNormalize4

Package: mu-cade Version: 0.11.dfsg1-8+b2 Severity: grave I have just noticed that mu-cade in testing and unstable is unusable because it crashes on startup with ODE INTERNAL ERROR 1: assertion "bNormalizationResult" failed in _dNormalize4() [odemath.h:42] [1]1120 abort (core dumped) mu-cad

Bug#804888: djview plugin unusable in debian testing...

Not a simple one. We would have to try embedding a window and observe the discrepancy between the size reported by xwininfo and the size reported by the qt program. This seems very complex (and requires a X server..) Happy new year, btw :-) - L. On 12/29/15, 4:48 PM, "Barak A. Pearlmutter"

Bug#804888: djview plugin unusable in debian testing...

Is there any reliable way to test for the buggy version of Qt-5? Because if there is we could do something in debian/rules or some place like that to fall back to Qt-4.8 iff Qt-5 is unavailable or buggy.

Processed: tagging 804149

Processing commands for cont...@bugs.debian.org: > tags 804149 + patch Bug #804149 [sudo] CVE-2015-5602: Unauthorized privilege escalation in sudoedit Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 804149: http://bugs.debian.org/cgi-bin/bugrep

Bug#804149: fixed in sudo 1.8.15-1

On Fri, 2015-12-25 at 04:35 +, Ben Hutchings wrote: > On Fri, 2015-12-25 at 03:09 +, Ben Hutchings wrote: > > On Fri, 2015-12-25 at 02:53 +, Ben Hutchings wrote: > > > Control: reopen -1 > > > > > > On Thu, 24 Dec 2015 05:19:31 + Bdale Garbee wrote: > > > > Source: sudo > > > > So

Bug#705092: Current state of this bug?

Dear all, what's the current state of this bug? Can't one make silversearcher-ag conflict with python-ase and get rid of this? Cheers, Robin signature.asc Description: OpenPGP digital signature

Bug#746054: marked as done (twinkle: FTBFS: configure: error: Library requirements (libzrtpcpp >= 1.3.0) not met)

Your message dated Tue, 29 Dec 2015 15:25:01 -0500 with message-id <20151229202501.GA18632@alcyone> and subject line Re: twinkle: FTBFS: configure: error: Library requirements (libzrtpcpp >= 1.3.0) not met has caused the Debian Bug report #746054, regarding twinkle: FTBFS: configure: error: Librar

Bug#809359: redmine is outdated in Debian

Source: redmine Severity: grave It seems Redmine Debian package is seriously outdated in Debian. It shouldn't be shipped as such into Stretch, in my opinion, as it does not seem to follow any upstream stable branch (2.6, 3.0, or 3.1). I am also puzzled as to why this was shipped in Jessie in the

Bug#805835: marked as done (voxbo: Fails to build with GSL 2)

Your message dated Tue, 29 Dec 2015 19:46:57 + with message-id and subject line Bug#805835: fixed in voxbo 1.8.5~svn1246-2 has caused the Debian Bug report #805835, regarding voxbo: Fails to build with GSL 2 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#809350: linux-image-4.3.0-1-686-pae: SSDs report disk errors

Package: src:linux Version: 4.3.3-2 Severity: grave Justification: renders package unusable Dear Maintainer, When booted up the linux-image-4.3.0-1-686-pae package, 4 hosts started to report errors on the SSDs: Thinkpad X301,Intel X18-M/X25-M/X25-V G2 SSDs Thinkpad W700,Samsung SSD 840 EVO 120G

Bug#809285: marked as done (plexus-compiler: FTBFS: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.1 or one of its dependencies could not be resolved: Cannot access central)

Your message dated Tue, 29 Dec 2015 18:06:19 + with message-id and subject line Bug#809285: fixed in plexus-compiler 2.4-3 has caused the Debian Bug report #809285, regarding plexus-compiler: FTBFS: Plugin org.apache.maven.plugins:maven-release-plugin:2.5.1 or one of its dependencies could n

Bug#804184: torbrowser-launcher: It's still not fixed!

On 15-12-29 14:42:13, 24t350c254t0hc wrote: > The bug is still not fixed (half a month later). Please do something > about these constant problems. All the people working on this package are aware of this. In the meantime, please use the version out of jessie-backports. signature.asc Description

Processed: severity of 807965 is serious

Processing commands for cont...@bugs.debian.org: > severity 807965 serious Bug #807965 [fglrx-modules-dkms] fglrx-modules-dkms doesn't compile after upgrading kernel to linux-image-4.3.0-1-amd64 (4.3.1-1) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contac

Bug#806353: marked as done (django-picklefield: FTBFS with Django 1.9)

Your message dated Tue, 29 Dec 2015 17:33:36 +0100 with message-id <20151229163336.ga29...@home.ouaza.com> and subject line Re: Processed (with 1 error): reassign 806353 to src:python-django, merging 806353 807683 has caused the Debian Bug report #806353, regarding django-picklefield: FTBFS with D

Bug#806354: marked as done (django-polymorphic: FTBFS with Django 1.9)

Your message dated Tue, 29 Dec 2015 15:37:29 + with message-id and subject line Bug#806354: fixed in django-polymorphic 0.8.1-1 has caused the Debian Bug report #806354, regarding django-polymorphic: FTBFS with Django 1.9 to be marked as done. This means that you claim that the problem has be

Bug#809133: marked as done (ggcov: FTBFS: ERROR: (test001) tggcov failed, see log or re-run with -D all,verbose --no-log)

Your message dated Tue, 29 Dec 2015 14:32:28 + with message-id and subject line Bug#809133: fixed in ggcov 0.9-10 has caused the Debian Bug report #809133, regarding ggcov: FTBFS: ERROR: (test001) tggcov failed, see log or re-run with -D all,verbose --no-log to be marked as done. This means

Processed: Re: Bug#809136: probably not suitable to be packaged in debian

Processing control commands: > severity -1 serious Bug #809136 [borgbackup] probably not suitable to be packaged in debian Severity set to 'serious' from 'important' -- 809136: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809136 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Bug#804184: torbrowser-launcher: It's still not fixed!

Package: torbrowser-launcher Version: 0.1.9-1+deb8u1 Followup-For: Bug #804184 Dear Maintainer, The bug is still not fixed (half a month later). Please do something about these constant problems. # torbrowser-launcher Gtk-Message: Failed to load module "canberra-gtk-module" Tor Browser Launcher

Bug#796932: marked as done (hhvm: FTBFS on buildds (unsatisfiable libjpeg62-dev build-dep))

Your message dated Tue, 29 Dec 2015 12:34:58 + with message-id and subject line Bug#796932: fixed in hhvm 3.11.0+dfsg-1 has caused the Debian Bug report #796932, regarding hhvm: FTBFS on buildds (unsatisfiable libjpeg62-dev build-dep) to be marked as done. This means that you claim that the p

Bug#808490: marked as done (haskell-certificate: FTBFS with ghc 7.10(?): Non type-variable argument in the constraint: MonadError [Char] m)

Your message dated Tue, 29 Dec 2015 12:02:49 + with message-id and subject line Bug#807541: Removed package(s) from unstable has caused the Debian Bug report #808490, regarding haskell-certificate: FTBFS with ghc 7.10(?): Non type-variable argument in the constraint: MonadError [Char] m to be

Bug#752961: marked as done (vor: FTBFS - missing -lm)

Your message dated Tue, 29 Dec 2015 11:58:49 + with message-id and subject line Bug#809267: Removed package(s) from unstable has caused the Debian Bug report #752961, regarding vor: FTBFS - missing -lm to be marked as done. This means that you claim that the problem has been dealt with. If th

Processed: your mail

Processing commands for cont...@bugs.debian.org: > found 788723 1.11.6-1 Bug #788723 [src:icinga] [src:icinga] Some sources are not included in your package Marked as found in versions icinga/1.11.6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 788723: http:

Bug#802166: otags: fails to install: post-installation script returned error exit status 3

Mehdi Dogguy writes: > Can you give us a hint on how to work out a real fix for this issue? I am looking at it now. There is quite a bit new syntax in 4.02, yielding quite a few warnings about incomplete pattern in otags. Each of these will crash otags in the same way, for instance attributes, e

Bug#797526: upstream status

On Tue, Dec 29, 2015 at 09:09:37AM +, olivier sallou wrote: > upstream has not updated this and is not in their priority Do you think the hint by Gianfranco Costamagna https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797526#15 which I implemented as patch in SVN would work? You could ru

Bug#807019: tracking bin-num - broken unison due to binnmu upload

On Tue, 29 Dec 2015, Alexandre Rossi wrote: > Hi, > > >> The change done in unison 2.48 to overcome this looks pretty big... I'm > >> not sure I'll be able/willing to provide a unison2.40.102 any more. > >> Moreover, this package was created to provide compatibility with > >> previous Debian rele

Bug#807019: tracking bin-num - broken unison due to binnmu upload

Hi, >> The change done in unison 2.48 to overcome this looks pretty big... I'm >> not sure I'll be able/willing to provide a unison2.40.102 any more. >> Moreover, this package was created to provide compatibility with >> previous Debian releases, but another change in OCaml 4.02 makes it >> incomp

Bug#786165: This bug is not RC

Mattia, thanks again for your work.

Bug#809286: marked as done (python-pywcs: FTBFS: wcslib_wrap.c:2937:5: error: invalid use of undefined type 'struct tabprm')

Your message dated Tue, 29 Dec 2015 09:48:57 + with message-id and subject line Bug#809286: fixed in python-pywcs 1.12-3 has caused the Debian Bug report #809286, regarding python-pywcs: FTBFS: wcslib_wrap.c:2937:5: error: invalid use of undefined type 'struct tabprm' to be marked as done. T

Bug#784070: Stable is still affected

The package has been uploaded to jessie-proposed-updates thanks to Adam D. Barratt and Gianfranco Costamagna. You can (and I encourage you to ;-)) test the package following the instructions on the stable-proposed-updates wiki page (https://www.debian.org/releases/proposed-updates). Please confirm

Bug#797526: upstream status

upstream has not updated this and is not in their priority

Bug#786165: This bug is not RC

On Tue, Dec 29, 2015 at 10:09:35AM +0800, Rolf Leggewie wrote: > This bug was not RC at the first time you marked it as such. It was not > RC at the time I downgraded it back to non-RC. You were even > specifically told *not* to mark bugs prematurely as RC in 746741 with > regards to the removal

Processed: fixed 800813 43.0

Processing commands for cont...@bugs.debian.org: > fixed 800813 43.0-1 Bug #800813 {Done: Sylvestre Ledru } [iceweasel] Creating or renaming a bookmark overwrites other bookmarks Marked as fixed in versions iceweasel/43.0-1. > thanks Stopping processing here. Please contact me if you need assist

Bug#800813: marked as done (Creating or renaming a bookmark overwrites other bookmarks)

Your message dated Tue, 29 Dec 2015 09:19:39 +0100 with message-id <5682421b.7060...@mozilla.com> and subject line Re: Bug#800813: Fixed has caused the Debian Bug report #800813, regarding Creating or renaming a bookmark overwrites other bookmarks to be marked as done. This means that you claim th

Processed: Re: Bug#800813: Fixed

Processing commands for cont...@bugs.debian.org: > fixed 800813 43.0 Bug #800813 [iceweasel] Creating or renaming a bookmark overwrites other bookmarks There is no source info for the package 'iceweasel' at version '43.0' with architecture '' Unable to make a source version for version '43.0' Ma