Debian Bug report logs - #379682
ITA: mercury -- A new logic/functional programming language

Toggle useless messages

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

From: Mohammed Adnène Trojette <adn+deb@diwi.org>

To: submit@bugs.debian.org

Subject: O: mercury -- A new logic/functional programming language

Date: Tue, 25 Jul 2006 00:58:03 +0200

Package: wnpp
Severity: normal

The current maintainer of mercury, Peter Hawkins <peterh@debian.org>,
has orphaned this package.

If you want to be the new maintainer, please take it -- see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: mercury
Binary: mercury, mercury-doc
Version: 0.11.0.rotd.20040511-5
Priority: optional
Section: devel
Maintainer: Peter Hawkins <peterh@debian.org>
Build-Depends: debhelper (>= 4.0.0), autotools-dev
Architecture: any
Standards-Version: 3.6.1
Format: 1.0
Directory: pool/main/m/mercury
Files:
 1627b56d6911456f627e52617cf56ef6 555 mercury_0.11.0.rotd.20040511-5.dsc
 1bae4aa44e741223346fa323a8cb0dc1 20910227 mercury_0.11.0.rotd.20040511-5.tar.gz

Package: mercury
Priority: optional
Section: devel
Installed-Size: 109388
Maintainer: Peter Hawkins <peterh@debian.org>
Architecture: i386
Version: 0.11.0.rotd.20040511-5
Depends: libc6 (>= 2.3.2.ds1-4), make
Conflicts: mmake
Filename: pool/main/m/mercury/mercury_0.11.0.rotd.20040511-5_i386.deb
Size: 25313164
MD5sum: 2a0d3c1ccb80f4c36e01c5c867a84c56
SHA1: 6e2b882a8640d42b33644bf5f830d196d5b8cd35
SHA256: 6959bbe494e77a5a29e64b58448a3518f80189b3de74dcf58a115d5e26ea9fcb
Description: A new logic/functional programming language
 Mercury is a new 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.
 .
 This package contains all the files required for developing programs
 in the Mercury language.

Package: mercury-doc
Priority: optional
Section: devel
Installed-Size: 2096
Maintainer: Peter Hawkins <peterh@debian.org>
Architecture: all
Source: mercury
Version: 0.11.0.rotd.20040511-5
Filename: pool/main/m/mercury/mercury-doc_0.11.0.rotd.20040511-5_all.deb
Size: 965914
MD5sum: 7c87c1e18f13590da15a35a6b54338da
SHA1: 9bf1cf4ddb872060319fe63a598b780bd681409a
SHA256: 853ae26e8199a2d6e7b58acd69e699185e8d6e1e3ba96367e3aefe55e6a7be04
Description: Documentation for mercury
 Mercury is a new 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.
 .
 This package contains the documentation for the Mercury compiler.
Tag: role::content:doc

-- 
adn
Mohammed Adnène Trojette

Message #14 received at 379682@bugs.debian.org (full text, mbox, reply):

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

To: Roy Ward <royward770@actrix.co.nz>

Cc: 379682@bugs.debian.org

Date: Thu, 24 Jan 2008 15:14:05 +1100

Hi Roy Ward,

I'm interested in seeing some up to date Mercury packages in Debian.   
Preferably with separate binary packages for the complier and each  
supported grade.

How are you going with adoption of this package?

Thanks.

Message #23 received at 379682@bugs.debian.org (full text, mbox, reply):

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

To: Barry deFreese <bddebian@comcast.net>

Cc: 446665@bugs.debian.org, royward770@actrix.co.nz, debian-qa@lists.debian.org, 379682@bugs.debian.org, mercury-developers@csse.unimelb.edu.au

Subject: Re: mercury: should this package be removed?

Date: Wed, 20 Feb 2008 09:50:44 +1100

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 the Mecury website, it is supposed to build with 
> gcc-4.1 which would be a hell of a lot better than gcc-3.x.
> 
> Is that not the case?  This thing has been orphaned a while and has an 
> RC bug over a year old.  If no-one wants to fix it up, I will request 
> removal within the week.
> 
> If I can help with packaging or fixing this thing, please feel free to 
> contact me and will gladly help if I can.  Otherwise it's a goner. :-)
> 

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.

The Mercury website should be considered correct, this package (in
debian) is a very old version of Mercury and I'd like to release a newer
package based on the current stable version, and also ensure I can
produce .debs for the current CVS HEAD.

There are several components to mercury that I'd like to package in
seperate binary packages.  These are:
    + Complier
    + Runtime and Standard Library
    + Other tools such as debuggers and profilers.

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 backend and a MSIL backend.  Options can include
optional garbage collection (as apposed to never reclaiming memory),
profiling support, debugging support and more.

I'd like to package the library and runtime for each grade.  These can
all be installed concurrently and won't conflict.

This will mean that there may be 6-12 mercury-related packages.  And
since I haven't packaged for Debian before this is rather an ominous
task.  I intend to read plenty of documentation and seek the help of
debian-mentors@debian.org as appropriate.

I usually use the ROTD releases, however that's mostly because I'm
working on Mercury it's self.  It is probably useful to package a stable
release and a ROTD, since we havn't made a release for a while.

Unfortunatly I can't make any progress of when this will be done, and
I'm not yet sure the best way to do it.  Will removing the old package
from Debian make it harder for me to get this one in?  If so I'd like it
left in Debian until I'm able to complete this.  But since I want to
package the new stable version instead removing it may not affect me.

Ray Ward:  I'd like to addopt this, may I?  If you agree I'll change O
to ITA and make myself the owner on bug #379682.

I've also CC'ed the mercury-developers@csse.unimelb.edu.au mailing list.

Thanks.

Message #28 received at 379682@bugs.debian.org (full text, mbox, reply):

From: Roy Ward <royward770@actrix.co.nz>

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

Cc: Barry deFreese <bddebian@comcast.net>, 446665@bugs.debian.org, debian-qa@lists.debian.org, 379682@bugs.debian.org, mercury-developers@csse.unimelb.edu.au

Subject: Re: mercury: should this package be removed?

Date: Wed, 20 Feb 2008 13:18:01 +1300

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 mercury-related packages.  And
> since I haven't packaged for Debian before this is rather an ominous
> task.  I intend to read plenty of documentation and seek the help of
> debian-mentors@debian.org as appropriate.

I'm in a similar position - not much time, and have never created a Debian package before. I was going to create one big 
package, but 6-12 makes more sense.

> I usually use the ROTD releases, however that's mostly because I'm
> working on Mercury it's self.  It is probably useful to package a stable
> release and a ROTD, since we havn't made a release for a while.

One of the reasons that the previous version never made it to stable was that was an ROTD, so I see using a ROTD only as 
a bit of a trap. Packaging both might be good though, but only have the release version go into Lenny.

> Unfortunatly I can't make any progress of when this will be done, and
> I'm not yet sure the best way to do it.  Will removing the old package
> from Debian make it harder for me to get this one in?  If so I'd like it
> left in Debian until I'm able to complete this.  But since I want to
> package the new stable version instead removing it may not affect me.

I was involved in discussions on this a while ago (when I put in the ITA) and my thought was to leave it in so the bug 
history etc. doesn't get removed (some it it is still relevant). Taking it over might also make it easier to get a 
sponsor if you are not a Debian dev. It would also be nice not to have another package grab the name. However the 
maintainers have the final say on that.

> Ray Ward:  I'd like to addopt this, may I?  If you agree I'll change O
> to ITA and make myself the owner on bug #379682.

Absolutely, particularly as my ITA was quite some time ago, and I've still not managed to get a package ready. It sounds 
like we are in similar positions time and experience wise, and you have the advantage of being a developer - I've only 
been a user for a few years. My main interest is to see that a reasonably recent Mercury package gets into Debian.

With what limited time I've got, I'm also happy to help in any way I can.

Cheers,
Roy Ward.

Message #37 received at 379682@bugs.debian.org (full text, mbox, reply):

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

To: Barry deFreese <bddebian@comcast.net>

Cc: Roy Ward <royward770@actrix.co.nz>, mercury-developers@csse.unimelb.edu.au, 379682@bugs.debian.org

Subject: Re: mercury: should this package be removed?

Date: Wed, 27 Feb 2008 10:40:47 +1100

On 27/02/2008, at 5:07 AM, Barry deFreese wrote:
>
> As I mentioned yesterday I have a package that is now building with  
> gcc-4.1 with all of the grades that the current package has.   
> However, the package still has several issues.  One of the biggies  
> is that it is creating self-recursive symlinks in /usr/lib/mercury/ 
> ints/Mercury/{int2s, int3s, ints, mihs, module_deps, opts,  
> trans_opts}  all which link to ..
>
> Any idea what that is for and if it is even necessary or what it is  
> supposed to be doing?
>
> As for maintaining this in some VCS system, that shouldn't be an  
> issue.  Just make sure you keep the debian and VCS dirs/files out  
> of the tarball.
>
> Any help/advice would be greatly appreciated.

Barry,

It seems that about 3 of us are creating packages independently.   
Please allow me to coordinate everybody's efforts.  I have a darcs  
repository[1] of what I've achieved so far (the dh_install step fails  
atm).  If you'd like please check it out, make any changes and use  
'darcs send' to e-mail them to me.

Otherwise e-mail what you've done so far and I'll take a look.

I expect you've gotten a little further than me, however I don't know  
what approach you are taking and what outcomes you're aiming for, so  
accepting your work may take longer than expected.

I'm building mercury for a single grade initially just to get  
something working, this will be asm_fast.gc.  I'm also building  
separate packages such as mercury-dev mercury-asmfastgc1-dev mercury- 
bin.

I'd be very interested to see what you have achieved.


1: http://www.digitalerection.com/~paul/mercury-0.13.1-debianization
This is the debian directory.  There are also some patches for  
mercury that aren't published yet.

Message #42 received at 379682@bugs.debian.org (full text, mbox, reply):

From: Barry deFreese <bddebian@comcast.net>

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

Cc: Roy Ward <royward770@actrix.co.nz>, mercury-developers@csse.unimelb.edu.au, 379682@bugs.debian.org

Subject: Re: mercury: should this package be removed?

Date: Tue, 26 Feb 2008 21:28:05 -0500

Paul Bone wrote:
>
> On 27/02/2008, at 5:07 AM, Barry deFreese wrote:
>>
>> As I mentioned yesterday I have a package that is now building with 
>> gcc-4.1 with all of the grades that the current package has.  
>> However, the package still has several issues.  One of the biggies is 
>> that it is creating self-recursive symlinks in 
>> /usr/lib/mercury/ints/Mercury/{int2s, int3s, ints, mihs, module_deps, 
>> opts, trans_opts}  all which link to ..
>>
>> Any idea what that is for and if it is even necessary or what it is 
>> supposed to be doing?
>>
>> As for maintaining this in some VCS system, that shouldn't be an 
>> issue.  Just make sure you keep the debian and VCS dirs/files out of 
>> the tarball.
>>
>> Any help/advice would be greatly appreciated.
>
> Barry,
>
> It seems that about 3 of us are creating packages independently.  
> Please allow me to coordinate everybody's efforts.  I have a darcs 
> repository[1] of what I've achieved so far (the dh_install step fails 
> atm).  If you'd like please check it out, make any changes and use 
> 'darcs send' to e-mail them to me.
>
> Otherwise e-mail what you've done so far and I'll take a look.
>
> I expect you've gotten a little further than me, however I don't know 
> what approach you are taking and what outcomes you're aiming for, so 
> accepting your work may take longer than expected.
>
> I'm building mercury for a single grade initially just to get 
> something working, this will be asm_fast.gc.  I'm also building 
> separate packages such as mercury-dev mercury-asmfastgc1-dev mercury-bin.
>
> I'd be very interested to see what you have achieved.
>
>
> 1: http://www.digitalerection.com/~paul/mercury-0.13.1-debianization
> This is the debian directory.  There are also some patches for mercury 
> that aren't published yet.
>
Paul,

Ah great, I didn't know you were actively working on it.  I will stop 
then since I'm not that familiar with mecury.

I've uploaded my source package that you can pull from here: 
http://mentors.debian.net/debian/pool/main/m/mercury/mercury_0.13.1-1.dsc

I'm happy to help with any packaging issues you have (if I can help).

Thanks,

Barry deFreese

Message #47 received at 379682-close@bugs.debian.org (full text, mbox, reply):

From: Thomas Huriaux <thomas.huriaux@gmail.com>

To: 379682-close@bugs.debian.org

Subject: Package removed

Date: Sat, 24 May 2008 10:56:23 +0200

mercury was removed from the archive (see #446665).

-- 
Thomas Huriaux

Send a report that this bug log contains spam.