Bug#446665: mercury: should this package be removed?

2008-05-05 Thread Lucas Nussbaum
severity 446665 normal reassign 446665 ftp.debian.org retitle 446665 RM: mercury -- RoQA; RC buggy thanks On 14/10/07 at 20:32 +0200, Lucas Nussbaum wrote: Your package came up as a candidate for removal from Debian, because: * 4 RC bugs opened for a long time * not suitable for a stable

Processed: Re: Bug#446665: mercury: should this package be removed?

2008-05-05 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: severity 446665 normal Bug#446665: mercury: should this package be removed? Severity set to `normal' from `serious' reassign 446665 ftp.debian.org Bug#446665: mercury: should this package be removed? Bug reassigned from package `mercury

Bug#446665: mercury: should this package be removed?

2008-02-20 Thread Paul Bone
On Wed, Feb 20, 2008 at 06:43:27PM +1100, Peter Hawkins wrote: Hi... On Feb 20, 2008 9:50 AM, Paul Bone [EMAIL PROTECTED] wrote: Mercury also supports 'grades', this makes it different to other compliers and more interesting to package. Each grade represents a complier backend and some

Bug#446665: mercury: should this package be removed?

2008-02-19 Thread Barry deFreese
Hi folks, Sorry for all of the CCs but all of you have expressed interest in fixing/adopting this package (with the exception of QA). Do any of you still have an interest and/or a plan to fix this package? According to the Mecury website, it is supposed to build with gcc-4.1 which would

Bug#446665: mercury: should this package be removed?

2008-02-19 Thread Roy Ward
I filed the initial ITA, but have then been unable to make much progress because of other commitments (including being overseas for a while). Unfortunately, although I'm back now, unforeseen personal circumstances mean I won't be able to do anything in the immediate future (next 2-3 weeks at

Bug#446665: mercury: should this package be removed?

2008-02-19 Thread Paul Bone
On Tue, Feb 19, 2008 at 03:27:37PM -0500, Barry deFreese wrote: Hi folks, Sorry for all of the CCs but all of you have expressed interest in fixing/adopting this package (with the exception of QA). Do any of you still have an interest and/or a plan to fix this package? According to

Bug#446665: mercury: should this package be removed?

2008-02-19 Thread Roy Ward
Paul Bone wrote: Hi Barry. I'm interested in re-packaging this, however it's going to be one of those things that gets a small amount of attention here and there. I'm one of the Mercury developers, so I use and develop on Mercury day-to-day. This will mean that there may be 6-12

Bug#446665: mercury: should this package be removed?

2008-02-19 Thread Peter Hawkins
Hi... On Feb 20, 2008 9:50 AM, Paul Bone [EMAIL PROTECTED] wrote: Mercury also supports 'grades', this makes it different to other compliers and more interesting to package. Each grade represents a complier backend and some options. There are two C backends, a Java backend, and Erlang

Bug#446665: mercury: should this package be removed?

2007-12-12 Thread Lucas Nussbaum
On 30/11/07 at 17:22 +1300, Roy Ward wrote: Lucas Nussbaum wrote: Have you made some progress on this package? Some, but not enough to submit a package. One bit of news is that gcc-3.3 is going to be the required compiler. I've looking at building Mercury 0.13.1 with several versions of

Bug#446665: mercury: should this package be removed?

2007-12-12 Thread Roy Ward
Lucas Nussbaum wrote: I don't know anything about mercury, but maybe it would be a better plan to package rotds, and find and fix bugs in them, instead of trying to get an old version in debian, and then switching to a brand new release just before lenny. Note that you could also decide to

Processed: Re: Bug#446665: mercury: should this package be removed?

2007-11-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: notfixed 446665 0.11.0.rotd.20040511-5 Bug#446665: mercury: should this package be removed? Bug no longer marked as fixed in version 0.11.0.rotd.20040511-5. found 446665 0.11.0.rotd.20040511-5 Bug#446665: mercury: should this package be removed? Bug

Bug#446665: mercury: should this package be removed?

2007-11-29 Thread Lucas Nussbaum
notfixed 446665 0.11.0.rotd.20040511-5 found 446665 0.11.0.rotd.20040511-5 thanks On 15/10/07 at 00:38 +0200, Lucas Nussbaum wrote: Hi Roy, On 15/10/07 at 11:03 +1300, Roy Ward wrote: * New upstream release available for a long time now I'm working on packaging that - it's still going

Bug#446665: mercury: should this package be removed?

2007-11-29 Thread Roy Ward
Lucas Nussbaum wrote: Have you made some progress on this package? Some, but not enough to submit a package. One bit of news is that gcc-3.3 is going to be the required compiler. I've looking at building Mercury 0.13.1 with several versions of gcc on x86 and amd64, and while projects are fine

Bug#446665: mercury: should this package be removed?

2007-10-14 Thread Lucas Nussbaum
Package: mercury Version: 0.11.0.rotd.20040511-5 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, Your package came up as a candidate for removal from Debian, because: * 4 RC bugs opened for a long time * not suitable for a stable release according to #281369 * Low

Bug#446665: mercury: should this package be removed?

2007-10-14 Thread Roy Ward
Lucas Nussbaum wrote: Package: mercury Version: 0.11.0.rotd.20040511-5 Severity: serious User: [EMAIL PROTECTED] Usertags: proposed-removal Hi, Your package came up as a candidate for removal from Debian, because: * 4 RC bugs opened for a long time Of the bugs: * #281369: Dummy RC bug

Bug#446665: mercury: should this package be removed?

2007-10-14 Thread Lucas Nussbaum
Hi Roy, On 15/10/07 at 11:03 +1300, Roy Ward wrote: * New upstream release available for a long time now I'm working on packaging that - it's still going to take some time (in the order of weeks). If you think that it should be orphaned instead of being removed from Debian, please