Debian Bug report logs - #538802
RFP: mercury -- The Mercury programming system, a pure logical/functional programming language.

Package: wnpp; Maintainer for wnpp is wnpp@debian.org;

Reported by: Paul Bone <pbone@csse.unimelb.edu.au>

Date: Mon, 27 Jul 2009 07:36:10 UTC

Severity: wishlist

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, debian-devel@lists.debian.org, <wnpp@debian.org>:
Bug#538802; Package wnpp. (Mon, 27 Jul 2009 07:36:13 GMT) Full text and rfc822 format available.

Acknowledgement sent to Paul Bone <pbone@csse.unimelb.edu.au>:
New Bug report received and forwarded. Copy sent to debian-devel@lists.debian.org, <wnpp@debian.org>. (Mon, 27 Jul 2009 07:36:13 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Paul Bone <pbone@csse.unimelb.edu.au>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
Date: Mon, 27 Jul 2009 17:34:44 +1000
Package: wnpp
Severity: wishlist
Owner: Paul Bone <pbone@csse.unimelb.edu.au>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


* Package name    : mercury
  Version         : 0.13.1-rotd20090725
  Upstream Author : Mercury Group <mercury@csse.unimelb.edu.au>
* URL             : http://www.mercury.csse.unimelb.edu.au/
* License         : GPL2
  Programming Lang: Mercury
  Description     : The Mercury programming system, a pure logical/functional programming language.

 Mercury is a logic/functional programming language, which combines
 the clarity and expressiveness of declarative programming with advanced
 static analysis and error detection features.  Its highly optimized
 execution algorithm delivers efficiency far in excess of existing logic
 programming systems, and close to conventional programming
 systems. Mercury addresses the problems of large-scale program
 development, allowing modularity, separate compilation, and numerous
 optimization/time trade-offs.

- -- System Information:
Debian Release: 5.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkptWJAACgkQ5BL8BUmFfuXH+ACfX/iUhm+zlv0V85zTT/QXzNHg
R8oAoI3JqP0TdK3p75QkCesNUgnwogDs
=bi3e
-----END PGP SIGNATURE-----




Information forwarded to debian-bugs-dist@lists.debian.org, <wnpp@debian.org>, Paul Bone <pbone@csse.unimelb.edu.au>:
Bug#538802; Package wnpp. (Mon, 27 Jul 2009 17:18:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to "brian m. carlson" <sandals@crustytoothpaste.ath.cx>:
Extra info received and forwarded to list. Copy sent to <wnpp@debian.org>, Paul Bone <pbone@csse.unimelb.edu.au>. (Mon, 27 Jul 2009 17:18:03 GMT) Full text and rfc822 format available.

Message #10 received at 538802@bugs.debian.org (full text, mbox):

From: "brian m. carlson" <sandals@crustytoothpaste.ath.cx>
To: debian-devel@lists.debian.org, 538802@bugs.debian.org
Subject: Re: Bug#538802: ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
Date: Mon, 27 Jul 2009 17:13:06 +0000
[Message part 1 (text/plain, inline)]
On Mon, Jul 27, 2009 at 05:34:44PM +1000, Paul Bone wrote:
> * Package name    : mercury
>   Version         : 0.13.1-rotd20090725
>   Upstream Author : Mercury Group <mercury@csse.unimelb.edu.au>
> * URL             : http://www.mercury.csse.unimelb.edu.au/
> * License         : GPL2
>   Programming Lang: Mercury
>   Description     : The Mercury programming system, a pure logical/functional programming language.

This used to be in Debian some time ago, because I remember trying to
work on the package for some reason.  I believe that it is
self-hosting[0], which may be a problem, except that it supposedly comes
with a C version of the compiler as well.  To make life easy for porters,
I'd request that you always build the C compiler and then, if you want
to, bootstrap the Mercury compiler from that.

If I'm remembering incorrectly, or that's no longer the case, feel free
to disregard this.

[0] That is, the compiler is written in Mercury.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
+1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only
OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, <wnpp@debian.org>:
Bug#538802; Package wnpp. (Tue, 28 Jul 2009 01:00:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Paul Bone <pbone@csse.unimelb.edu.au>:
Extra info received and forwarded to list. Copy sent to <wnpp@debian.org>. (Tue, 28 Jul 2009 01:00:02 GMT) Full text and rfc822 format available.

Message #15 received at 538802@bugs.debian.org (full text, mbox):

From: Paul Bone <pbone@csse.unimelb.edu.au>
To: debian-devel@lists.debian.org, 538802@bugs.debian.org
Subject: Re: Bug#538802: ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
Date: Tue, 28 Jul 2009 10:58:32 +1000
[Message part 1 (text/plain, inline)]
On Mon, Jul 27, 2009 at 05:13:06PM +0000, brian m. carlson wrote:
> On Mon, Jul 27, 2009 at 05:34:44PM +1000, Paul Bone wrote:
> > * Package name    : mercury
> >   Version         : 0.13.1-rotd20090725
> >   Upstream Author : Mercury Group <mercury@csse.unimelb.edu.au>
> > * URL             : http://www.mercury.csse.unimelb.edu.au/
> > * License         : GPL2
> >   Programming Lang: Mercury
> >   Description     : The Mercury programming system, a pure logical/functional programming language.
> 
> This used to be in Debian some time ago, because I remember trying to
> work on the package for some reason.  I believe that it is
> self-hosting[0], which may be a problem, except that it supposedly comes
> with a C version of the compiler as well.  To make life easy for porters,
> I'd request that you always build the C compiler and then, if you want
> to, bootstrap the Mercury compiler from that.
> 
> If I'm remembering incorrectly, or that's no longer the case, feel free
> to disregard this.
> 

This is mostly correct.  Mercury is indeed self-hosting and was
previously included in Debian.  Mercury has a number of different
backends two of these target C, high-level C and low-level C.  The
Mercury source distribution includes C intermediate files for the
standard library and compiler generated by the low-level C backend,
these can be compiled with GCC to generate binaries which can be used to
bootstrap an installation by re-compiling the Mercury sources.

I have a working Debian package that builds and bootstraps Mercury from
the source distribution.  It requires gcc-3.4 as a build-depend and is
able to bootstrap itself so that the resulting binaries are optimal on
32bit and 64bit machines (the explanation involves a discussion of
tagged pointers).

I hope that this will be acceptable by the Debian project and that
distributing intermediate files in the .orig.tar.gz file is not a
problem.

Mercury should build from the Debian source package equally as well as
it can build from the upstream source distribution on all architectures.
Cross-compilation should not be necessary.

See also the list of supported architectures here:
http://www.mercury.csse.unimelb.edu.au/download/rotd.html

I hope this helps.  If you have any more questions please let us know.

Thanks.


[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, <wnpp@debian.org>:
Bug#538802; Package wnpp. (Tue, 28 Jul 2009 05:33:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Paul Bone <pbone@csse.unimelb.edu.au>:
Extra info received and forwarded to list. Copy sent to <wnpp@debian.org>. (Tue, 28 Jul 2009 05:33:02 GMT) Full text and rfc822 format available.

Message #20 received at 538802@bugs.debian.org (full text, mbox):

From: Paul Bone <pbone@csse.unimelb.edu.au>
To: 538802@bugs.debian.org
Subject: Mercury was removed from Debian in bug #446665
Date: Tue, 28 Jul 2009 15:29:57 +1000
[Message part 1 (text/plain, inline)]
Mercury was removed from Debian in Bug #446665

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, <wnpp@debian.org>, Paul Bone <pbone@csse.unimelb.edu.au>:
Bug#538802; Package wnpp. (Tue, 28 Jul 2009 06:36:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Reinhard Tartler <siretart@debian.org>:
Extra info received and forwarded to list. Copy sent to <wnpp@debian.org>, Paul Bone <pbone@csse.unimelb.edu.au>. (Tue, 28 Jul 2009 06:36:02 GMT) Full text and rfc822 format available.

Message #25 received at 538802@bugs.debian.org (full text, mbox):

From: Reinhard Tartler <siretart@debian.org>
To: Paul Bone <pbone@csse.unimelb.edu.au>
Cc: 538802@bugs.debian.org, debian-devel@lists.debian.org
Subject: Re: Bug#538802: ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
Date: Tue, 28 Jul 2009 08:35:14 +0200
Paul Bone <pbone@csse.unimelb.edu.au> writes:

> This is mostly correct.  Mercury is indeed self-hosting and was
> previously included in Debian.  Mercury has a number of different
> backends two of these target C, high-level C and low-level C.  The
> Mercury source distribution includes C intermediate files for the
> standard library and compiler generated by the low-level C backend,
> these can be compiled with GCC to generate binaries which can be used to
> bootstrap an installation by re-compiling the Mercury sources.
>
> I have a working Debian package that builds and bootstraps Mercury from
> the source distribution.  It requires gcc-3.4 as a build-depend and is
> able to bootstrap itself so that the resulting binaries are optimal on
> 32bit and 64bit machines (the explanation involves a discussion of
> tagged pointers).
>
> I hope that this will be acceptable by the Debian project and that
> distributing intermediate files in the .orig.tar.gz file is not a
> problem.

The same applies to the package aspectc++, a package that I maintain
since some time. AspectC++ is a language extension for C++ for aspect
oriented programming (AOP). It is built on top of an C/C++ Parsing and
Manipulation framework (PUMA), where some functionality (e.g. support
for various GNU language extension) is implemented using AspectC++
aspects. There you have a pretty similar situation, and I'm doing a very
similar approach: Shipping intermediate files that can be processed with
gcc.

I suggest that you use these intermediate files only for compiling an
intermediate compiler for bootstrapping. With that compiler, redo all
intermediate files and build the binaries of the compiler that will
eventually end up in the package. This ensures that you'll end with a
working compiler on all architectures.

BTW, this approach was actually suggested to me by Lamont Jones a few
years ago. It seems to be a quite common approach, FWIW.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4




Information forwarded to debian-bugs-dist@lists.debian.org, <wnpp@debian.org>:
Bug#538802; Package wnpp. (Tue, 28 Jul 2009 06:45:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Paul Bone <pbone@csse.unimelb.edu.au>:
Extra info received and forwarded to list. Copy sent to <wnpp@debian.org>. (Tue, 28 Jul 2009 06:45:04 GMT) Full text and rfc822 format available.

Message #30 received at 538802@bugs.debian.org (full text, mbox):

From: Paul Bone <pbone@csse.unimelb.edu.au>
To: Reinhard Tartler <siretart@debian.org>
Cc: 538802@bugs.debian.org, debian-devel@lists.debian.org
Subject: Re: Bug#538802: ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
Date: Tue, 28 Jul 2009 16:43:16 +1000
[Message part 1 (text/plain, inline)]
On Tue, Jul 28, 2009 at 08:35:14AM +0200, Reinhard Tartler wrote:
> Paul Bone <pbone@csse.unimelb.edu.au> writes:
> 
> > This is mostly correct.  Mercury is indeed self-hosting and was
> > previously included in Debian.  Mercury has a number of different
> > backends two of these target C, high-level C and low-level C.  The
> > Mercury source distribution includes C intermediate files for the
> > standard library and compiler generated by the low-level C backend,
> > these can be compiled with GCC to generate binaries which can be used to
> > bootstrap an installation by re-compiling the Mercury sources.
> >
> > I have a working Debian package that builds and bootstraps Mercury from
> > the source distribution.  It requires gcc-3.4 as a build-depend and is
> > able to bootstrap itself so that the resulting binaries are optimal on
> > 32bit and 64bit machines (the explanation involves a discussion of
> > tagged pointers).
> >
> > I hope that this will be acceptable by the Debian project and that
> > distributing intermediate files in the .orig.tar.gz file is not a
> > problem.
> 
> The same applies to the package aspectc++, a package that I maintain
> since some time. AspectC++ is a language extension for C++ for aspect
> oriented programming (AOP). It is built on top of an C/C++ Parsing and
> Manipulation framework (PUMA), where some functionality (e.g. support
> for various GNU language extension) is implemented using AspectC++
> aspects. There you have a pretty similar situation, and I'm doing a very
> similar approach: Shipping intermediate files that can be processed with
> gcc.
> 
> I suggest that you use these intermediate files only for compiling an
> intermediate compiler for bootstrapping. With that compiler, redo all
> intermediate files and build the binaries of the compiler that will
> eventually end up in the package. This ensures that you'll end with a
> working compiler on all architectures.

Yep,  That's what we do.

> BTW, this approach was actually suggested to me by Lamont Jones a few
> years ago. It seems to be a quite common approach, FWIW.

Thanks.

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, <wnpp@debian.org>, Paul Bone <pbone@csse.unimelb.edu.au>:
Bug#538802; Package wnpp. (Tue, 28 Jul 2009 07:48:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Lucas Nussbaum <lucas@lucas-nussbaum.net>:
Extra info received and forwarded to list. Copy sent to <wnpp@debian.org>, Paul Bone <pbone@csse.unimelb.edu.au>. (Tue, 28 Jul 2009 07:48:05 GMT) Full text and rfc822 format available.

Message #35 received at 538802@bugs.debian.org (full text, mbox):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>
To: Paul Bone <pbone@csse.unimelb.edu.au>
Cc: debian-devel@lists.debian.org, 538802@bugs.debian.org
Subject: Re: Bug#538802: ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
Date: Tue, 28 Jul 2009 09:30:58 +0200
On 28/07/09 at 10:58 +1000, Paul Bone wrote:
> On Mon, Jul 27, 2009 at 05:13:06PM +0000, brian m. carlson wrote:
> > On Mon, Jul 27, 2009 at 05:34:44PM +1000, Paul Bone wrote:
> > > * Package name    : mercury
> > >   Version         : 0.13.1-rotd20090725
> > >   Upstream Author : Mercury Group <mercury@csse.unimelb.edu.au>
> > > * URL             : http://www.mercury.csse.unimelb.edu.au/
> > > * License         : GPL2
> > >   Programming Lang: Mercury
> > >   Description     : The Mercury programming system, a pure logical/functional programming language.
> > 
> > This used to be in Debian some time ago, because I remember trying to
> > work on the package for some reason.  I believe that it is
> > self-hosting[0], which may be a problem, except that it supposedly comes
> > with a C version of the compiler as well.  To make life easy for porters,
> > I'd request that you always build the C compiler and then, if you want
> > to, bootstrap the Mercury compiler from that.
> > 
> > If I'm remembering incorrectly, or that's no longer the case, feel free
> > to disregard this.
> > 
> 
> This is mostly correct.  Mercury is indeed self-hosting and was
> previously included in Debian.  Mercury has a number of different
> backends two of these target C, high-level C and low-level C.  The
> Mercury source distribution includes C intermediate files for the
> standard library and compiler generated by the low-level C backend,
> these can be compiled with GCC to generate binaries which can be used to
> bootstrap an installation by re-compiling the Mercury sources.
> 
> I have a working Debian package that builds and bootstraps Mercury from
> the source distribution.  It requires gcc-3.4 as a build-depend and is
> able to bootstrap itself so that the resulting binaries are optimal on
> 32bit and 64bit machines (the explanation involves a discussion of
> tagged pointers).

Hi,

gcc-3.4 is about to be removed from Debian (#536777). How do you plan to
deal with that?
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |




Information forwarded to debian-bugs-dist@lists.debian.org, <wnpp@debian.org>:
Bug#538802; Package wnpp. (Tue, 28 Jul 2009 08:09:04 GMT) Full text and rfc822 format available.

Acknowledgement sent to Paul Bone <pbone@csse.unimelb.edu.au>:
Extra info received and forwarded to list. Copy sent to <wnpp@debian.org>. (Tue, 28 Jul 2009 08:09:04 GMT) Full text and rfc822 format available.

Message #40 received at 538802@bugs.debian.org (full text, mbox):

From: Paul Bone <pbone@csse.unimelb.edu.au>
To: Lucas Nussbaum <lucas@lucas-nussbaum.net>
Cc: debian-devel@lists.debian.org, 538802@bugs.debian.org
Subject: Re: Bug#538802: ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
Date: Tue, 28 Jul 2009 17:48:07 +1000
[Message part 1 (text/plain, inline)]
On Tue, Jul 28, 2009 at 09:30:58AM +0200, Lucas Nussbaum wrote:
> On 28/07/09 at 10:58 +1000, Paul Bone wrote:
> > On Mon, Jul 27, 2009 at 05:13:06PM +0000, brian m. carlson wrote:
> > > On Mon, Jul 27, 2009 at 05:34:44PM +1000, Paul Bone wrote:
> > > > * Package name    : mercury
> > > >   Version         : 0.13.1-rotd20090725
> > > >   Upstream Author : Mercury Group <mercury@csse.unimelb.edu.au>
> > > > * URL             : http://www.mercury.csse.unimelb.edu.au/
> > > > * License         : GPL2
> > > >   Programming Lang: Mercury
> > > >   Description     : The Mercury programming system, a pure logical/functional programming language.
> > > 
> > > This used to be in Debian some time ago, because I remember trying to
> > > work on the package for some reason.  I believe that it is
> > > self-hosting[0], which may be a problem, except that it supposedly comes
> > > with a C version of the compiler as well.  To make life easy for porters,
> > > I'd request that you always build the C compiler and then, if you want
> > > to, bootstrap the Mercury compiler from that.
> > > 
> > > If I'm remembering incorrectly, or that's no longer the case, feel free
> > > to disregard this.
> > > 
> > 
> > This is mostly correct.  Mercury is indeed self-hosting and was
> > previously included in Debian.  Mercury has a number of different
> > backends two of these target C, high-level C and low-level C.  The
> > Mercury source distribution includes C intermediate files for the
> > standard library and compiler generated by the low-level C backend,
> > these can be compiled with GCC to generate binaries which can be used to
> > bootstrap an installation by re-compiling the Mercury sources.
> > 
> > I have a working Debian package that builds and bootstraps Mercury from
> > the source distribution.  It requires gcc-3.4 as a build-depend and is
> > able to bootstrap itself so that the resulting binaries are optimal on
> > 32bit and 64bit machines (the explanation involves a discussion of
> > tagged pointers).
> 
> Hi,
> 
> gcc-3.4 is about to be removed from Debian (#536777). How do you plan to
> deal with that?

We use a comple of GCC extensions that cause problems with more recent versions
of GCC, we can turn those off or use the high-level C backend.  Either way, we
can deal with it but we mightn't like to :-) since in some cases it will make
things slower, and we don't as yet have a way to prevent this in profiling and
debugging builds.

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org, Paul Bone <pbone@csse.unimelb.edu.au>:
Bug#538802; Package wnpp. (Sat, 19 Feb 2011 17:14:08 GMT) Full text and rfc822 format available.

Acknowledgement sent to Lucas Nussbaum <lucas@debian.org>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org, Paul Bone <pbone@csse.unimelb.edu.au>. (Sat, 19 Feb 2011 17:14:08 GMT) Full text and rfc822 format available.

Message #45 received at 538802@bugs.debian.org (full text, mbox):

From: Lucas Nussbaum <lucas@debian.org>
To: 538802@bugs.debian.org
Cc: control@bugs.debian.org
Subject: mercury: changing back from ITP to RFP
Date: Sat, 19 Feb 2011 17:03:58 +0000
retitle 538802 RFP: mercury -- The Mercury programming system, a pure logical/functional programming language.
noowner 538802
thanks

Hi,

This is an automatic email to change the status of mercury back from ITP
(Intent to Package) to RFP (Request for Package), because this bug hasn't seen
any activity during the last 6 months.

If you are still interested in adopting mercury, please send a mail to
<control@bugs.debian.org> with:

 retitle 538802 ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
 owner 538802 !
 thanks

However, it is not recommended to keep ITP for a long time without acting on
the package, as it might cause other prospective maintainers to refrain from
packaging that software. It is also a good idea to document your progress on
this ITP from time to time, by mailing <538802@bugs.debian.org>.

Thank you for your interest in Debian,
-- 
Lucas, for the QA team <debian-qa@lists.debian.org>




Changed Bug title to 'RFP: mercury -- The Mercury programming system, a pure logical/functional programming language.' from 'ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.' Request was from Lucas Nussbaum <lucas@debian.org> to control@bugs.debian.org. (Sat, 19 Feb 2011 17:16:50 GMT) Full text and rfc822 format available.

Removed annotation that Bug was owned by Paul Bone <pbone@csse.unimelb.edu.au>. Request was from Lucas Nussbaum <lucas@debian.org> to control@bugs.debian.org. (Sat, 19 Feb 2011 17:16:51 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#538802; Package wnpp. (Mon, 21 Feb 2011 01:57:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Paul Bone <pbone@csse.unimelb.edu.au>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org. (Mon, 21 Feb 2011 01:57:03 GMT) Full text and rfc822 format available.

Message #54 received at 538802@bugs.debian.org (full text, mbox):

From: Paul Bone <pbone@csse.unimelb.edu.au>
To: Lucas Nussbaum <lucas@lucas-nussbaum.net>
Cc: debian-devel@lists.debian.org, 538802@bugs.debian.org
Subject: Re: Bug#538802: ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
Date: Mon, 21 Feb 2011 11:35:36 +1100
[Message part 1 (text/plain, inline)]
On Tue, Jul 28, 2009 at 05:48:07PM +1000, Paul Bone wrote:
> On Tue, Jul 28, 2009 at 09:30:58AM +0200, Lucas Nussbaum wrote:
> > 
> > gcc-3.4 is about to be removed from Debian (#536777). How do you plan to
> > deal with that?
> 
> We use a comple of GCC extensions that cause problems with more recent versions
> of GCC, we can turn those off or use the high-level C backend.  Either way, we
> can deal with it but we mightn't like to :-) since in some cases it will make
> things slower, and we don't as yet have a way to prevent this in profiling and
> debugging builds.
> 

This has now been solved in newer upstream versions of Mercury.

Thanks.

[signature.asc (application/pgp-signature, inline)]

Changed Bug title to 'ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.' from 'RFP: mercury -- The Mercury programming system, a pure logical/functional programming language.' Request was from Paul Bone <pbone@csse.unimelb.edu.au> to control@bugs.debian.org. (Mon, 21 Feb 2011 01:57:06 GMT) Full text and rfc822 format available.

Owner recorded as Paul Bone <pbone@csse.unimelb.edu.au>. Request was from Paul Bone <pbone@csse.unimelb.edu.au> to control@bugs.debian.org. (Mon, 21 Feb 2011 01:57:07 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org, Paul Bone <pbone@csse.unimelb.edu.au>:
Bug#538802; Package wnpp. (Mon, 27 May 2013 14:10:19 GMT) Full text and rfc822 format available.

Acknowledgement sent to Lucas Nussbaum <lucas@debian.org>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org, Paul Bone <pbone@csse.unimelb.edu.au>. (Mon, 27 May 2013 14:10:19 GMT) Full text and rfc822 format available.

Message #63 received at 538802@bugs.debian.org (full text, mbox):

From: Lucas Nussbaum <lucas@debian.org>
To: 538802@bugs.debian.org
Cc: control@bugs.debian.org
Subject: mercury: changing back from ITP to RFP
Date: Mon, 27 May 2013 15:24:24 +0200
retitle 538802 RFP: mercury -- The Mercury programming system, a pure logical/functional programming language.
noowner 538802
tag 538802 - pending
thanks

Hi,

This is an automatic email to change the status of mercury back from ITP
(Intent to Package) to RFP (Request for Package), because this bug hasn't seen
any activity during the last 12 months.

If you are still interested in adopting mercury, please send a mail to
<control@bugs.debian.org> with:

 retitle 538802 ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.
 owner 538802 !
 thanks

However, it is not recommended to keep ITP for a long time without acting on
the package, as it might cause other prospective maintainers to refrain from
packaging that software. It is also a good idea to document your progress on
this ITP from time to time, by mailing <538802@bugs.debian.org>.

Thank you for your interest in Debian,
-- 
Lucas, for the QA team <debian-qa@lists.debian.org>



Changed Bug title to 'RFP: mercury -- The Mercury programming system, a pure logical/functional programming language.' from 'ITP: mercury -- The Mercury programming system, a pure logical/functional programming language.' Request was from Lucas Nussbaum <lucas@debian.org> to control@bugs.debian.org. (Mon, 27 May 2013 14:33:39 GMT) Full text and rfc822 format available.

Removed annotation that Bug was owned by Paul Bone <pbone@csse.unimelb.edu.au>. Request was from Lucas Nussbaum <lucas@debian.org> to control@bugs.debian.org. (Mon, 27 May 2013 14:33:39 GMT) Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, wnpp@debian.org:
Bug#538802; Package wnpp. (Tue, 28 May 2013 00:54:09 GMT) Full text and rfc822 format available.

Acknowledgement sent to Paul Bone <paul@bone.id.au>:
Extra info received and forwarded to list. Copy sent to wnpp@debian.org. (Tue, 28 May 2013 00:54:09 GMT) Full text and rfc822 format available.

Message #72 received at 538802@bugs.debian.org (full text, mbox):

From: Paul Bone <paul@bone.id.au>
To: 538802@bugs.debian.org
Subject: Some small Mercury Packaging progress.
Date: Tue, 28 May 2013 10:56:56 +1000
There is now a group effort to package Mercury.  A small amount of progress
has been put online here:

https://github.com/Mercury-Language/packaging

-- 
Paul Bone
http://www.bone.id.au



Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Sat Apr 19 07:15:47 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.