I manage the group that develops FIS GT.M upstream. Although there has been no evidence of activity on the Debian lists in the last six months, there has been activity upstream.
Here is the issue: just as it takes a gcc binary to compile gcc, building GT.M has a bootstrapping step and it takes a GT.M binary to build GT.M. This appears to be a catch-22 situation for GT.M (although it is apparently not a catch-22 situation for gcc). We have been trying to use Python for the bootstrap step, but still do not have a successful GT.M build yet. If you can advise us on a way to break out of the catch-22 situation - what it would essentially take is an initial exception to allow is to use a GT.M binary to build GT.M from source - we can make a lot more progress, and progress visible to you. Otherwise, please leave GT.M in the ITP stage, and once we are able to use Python successfully to build GT.M, there will be progress that is visible to you. Regards -- Bhaskar On 02/19/2011 12:05 PM, Lucas Nussbaum wrote: > > retitle 541207 RFP: gt.m -- Database Engine with Extreme Scalability > and Robustness > noowner 541207 > thanks > > Hi, > > This is an automatic email to change the status of gt.m 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 gt.m, please send a mail to > <cont...@bugs.debian.org> with: > > retitle 541207 ITP: gt.m -- Database Engine with Extreme Scalability > and Robustness > owner 541207 ! > 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 <541...@bugs.debian.org>. > > Thank you for your interest in Debian, > -- > Lucas, for the QA team <debian...@lists.debian.org> > > -- GT.M - Rock solid. Lightning fast. Secure. No compromises. _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _____________
