Bug Description

BRL-CAD is a free, open-source, cross-platform constructive solid geometry (CSG) solid modeling computer-aided design (CAD) system developed by the United States Army Research Laboratory under the BSD/LGPL license.

# Retitling to lowercase since this may produce confusions.
#
# I've seen a couple of WNPPs duplicated because people don't see
# packages with uppercase. Besides, Debian policy requires source
# packages in lowercase.
#
# This is the ITP bunch.

There is currently two open ITPs for the brlcad package (#289684
and #289632). Can you please determine which one of you will package it
for Debian (or if you are going to comaintain this package), set the
owners of the bugs accordingly and merge these two bugs?

On Thu, Feb 23, 2006 at 04:39:36PM +0100, Thomas Huriaux wrote:
> Hi,
>
> There is currently two open ITPs for the brlcad package (#289684
> and #289632). Can you please determine which one of you will package it

An ITP and RFP open on the same software at the same time? Sloppy...
I guess merely checking before opening new ITPs isn't enough and I
should do the same before renaming RFPs... Well, first come first
serve, so I'll merge away mine.

This is an automatic mail sent to close the ITP you have reported or
are involved with.

Your ITP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 365 days.
- It hasn't had any activity recently.

As this is an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not
intended by owners and submitters (like you) to be closed, for
example if the ITP is still of your interest, or there has been
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail <email address hidden>
with a body text like this:

reopen 289632
stop

Further comments on the work done in the bug sent to
<email address hidden> would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <email address hidden>.

BRL-CAD is a bit of a pain. It wants tcl/tk 8.5 or 8.6, and can't work
with Debian's itcl because it links with tcl/tk 8.4. But then BRL-CAD
can't work with the Debian tcl/tk 8.5 packages either. I guess we'll
need to wait for itcl 3.3 upstream, but the RC was more than two years
ago...

Also, it took quite a bit of doing to get ADRT to build, and I can't get
it to do anything useful. And it doesn't recognize that I have Java
installed. And the IGES importer crashed on me.

If you can solve these problems, I'd love to help, this looks like a
great package! But I think for now I'm going to leave BRL-CAD and focus
on Salomé...

BRL-CAD is a free, open-source, cross-platform constructive solid geometry (CSG) solid modeling computer-aided design (CAD) system developed by the United States Army Research Laboratory under the BSD/LGPL license.

Apologies in advance, as it's not clear what the impact of nominating something for release entails. I'd be glad to help resolve any remaining release issues for getting BRL-CAD fully integrated, though.

Reviewing needs-packaging bug reports I have concluded that this bug is likely a duplicate of bug 311405. It'd be great if you could help consolidate these bug reports by performing the following actions.

1. Examine both bug reports to determine if they are actually duplicates.
2. Determine which bug report is more complete - a more complete bug report will have a status of Confirmed, Triaged or In Progress, may be assigned to someone or may possess a bug watch.
3. Mark the other bug report a duplicate of the complete one by clicking 'Mark as duplicate' on the right hand side of the bug page.

Bug 311405 is definitely a duplicate of this bug. There have been 12 releases, 3 major, since the last update to 311405 so this original report is still probably the most relevant. While the other bug had a lot of "discussion", not much useful progress was made.

The latest efforts that I'm aware are by 'mafm' with his files accessible via SVN here: