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 against Mercury
explained below.
* #430313: ldbl128 transition for alpha, powerpc, sparc, s390
I'm reasonably sure that doesn't apply to Mercury as the language doesn't support long doubles, but I want to be certain
before closing this bug.
* #297217: mercury: FTBFS (amd64/gcc-4.0): invalid lvalue in assignment
* #381813: mercury: FTBFS: cannot stat `./debian/tmp/usr/lib/mercury/bin':
No such file or directory
For both of these, Mercury has _never_ worked with gcc-4.0 - it does work with gcc-3.4 (recommended by upstream),
gcc-4.1 or gcc-4.2 (my preferred version, but there's some issues and testing I need to work through).
* not suitable for a stable release according to #281369
I've checked with the previous maintainer and upstream on this one. The reason for the bug is that the previous
maintainer didn't want a 'release of the day' (Mercury has two available branches - the numbered releases, and the
'release of the day') getting into testing/stable. I intend to package only the numbered releases.
Upstream has no objections to this being packaged for Debian.
* Low popcon (19 insts)
I consider the current package is too old to be useful (I've been telling people to install from source rather than the
package). Also, as a logic programming language, it's unlikely to ever have a particularly high popcon.
* Hasn't been in testing for a very long time
See comments on bug #281369
* 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 reply to this bug and tell so.
This is confusing - I thought it was already orphaned, which is when I filed an
ITA.
<snip>
If you disagree and want to continue to maintain this package, please
just close this bug, preferably in an upload also fixing the other
issues.
Whether to remove or not in the meantime I'm not certain. What makes the most sense - to leave it in until I get upload
a replacement (for which I will need to find a sponsor), or remove it in the meantime and I can apply to get it added to
Debian as a fresh package? My preference would be to keep it, as upgrading a package will be easier than adding a new
one, and it means the name, bug history, description etc. gets kept, but I'm open to suggestions on that one. I will
close this bug in the meantime.
It's not an option to quickly release a partial fix, as Mercury is a reasonably large package (and it takes quite a
while to build) and I want to have something pretty much right before a sponsor gets to spend any time on it.
Cheers,
Roy Ward.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
