On Thu, 21 Feb 2008, Thijs Kinkhorst wrote:
Yes, but this doesn't seem like a high priority issue that is worthy of an upload on its own, but rather a tweak.
From the single package perspective you are right and I do not
expect you to close any wishlist bug immediately. From a Debian-Med QA perspective it would be nice and this is why I filed this bug report. I will do this also for other packages to just have a record what should be done in a reasonable time frame.
Yes, that could be an idea. However, as time passes, the question whether ctn should remain to be packaged gets stronger. There's the following trouble: - Upstream is essentially dead for 4 years now; - CTN only works with MySQL servers <= which are getting obsolete really
MySQL servers <= ? (what)
fast, and haven't been in Debian for subsequent releases.
Hmm, taht's bad.
I'm considering removal rather than moving it into the Debian-Med group maintenance, as I think the time of debian-med is a lot better spent on software that is being maintained and not suffering from extensive bit rot. What do you think?
Well, I personally think that I have no idea about DICOM and can not answer personaly. Popcon stats http://people.debian.org/~igloo/popcon-graphs/index.php?packages=ctn show that there are some real votes (not only installations just drawn in by med-imaging installations). So there is some need for it. Instead of considering a remove I would try to contact upstream about the reasons the installation was stalled / stopped and find out about the chances to prevent bit rot by finding people who might upgrade ctn to work with servers > ? (see the what above ;-) ). Kind regards and thanks for keeping us up to date Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
