CTN status

[Thijs Kinkhorst-4]

Hi all,

What is the current status of CTN? I see that Andreas has done some work in
the repository, can it be uploaded?

I'm inclined to file a release critical bug against ctn soon since I think it
shouldn't be in lenny in this form. Of course this bug can be closed by an
upload improving CTN. If there are any plans to upload soon I'd gladly hear
it and I'll refrain from filing such bug.


cheers,
Thijs


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Andreas Tille]

On Mon, 7 Jul 2008, Thijs Kinkhorst wrote:

> What is the current status of CTN? I see that Andreas has done some work in
> the repository, can it be uploaded?

When I left it for some other burning issues it was not fully working.
I think I was about to add the patch from Pablo Sau <psau@...>.
If I remember right the issue was that Pablo did the patch against a
patched version and I tried to sort out things cleanly.
I forgot what exactly was the issue - just building the package will
reveal the issues easily.  Perhaps talking to Pablo again might help
because he seemed to be close to the solution.

> I'm inclined to file a release critical bug against ctn soon since I think it
> shouldn't be in lenny in this form. Of course this bug can be closed by an
> upload improving CTN. If there are any plans to upload soon I'd gladly hear
> it and I'll refrain from filing such bug.

Any help is really apreciated because I'm completely overloaded with
DebConf preparation stuff.

Kind regards

            Andreas.

--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Andreas Tille]

On Wed, 9 Jul 2008, ARCHIRAD S.L. wrote:

> The patch I sent to you solves the mysql issue of imposibility of  ctn
> working  with
> mysql-server version >= 4.2 and I don't think it could interfere with other
> patching.

I think the problem was that I probably made some mistake in applying the
patch.  It wouold be great if somebody could have a look at current SVN
and sort out the things there.  CTN in our SVN as it is currently is a mess
compared to all other packaging we did for Debian Med because it merges
upstream an patches and I was not able to sort out the sequence of the
patch you applied (either against upstream source or patched Debian source.

Because I have no time at all to care for this problem I urge every
imaging interested person to have a look into this - we will loose
ctn soon if we are not able to act and upload a fixed package.
So please verify the patch in SVN - perhaps take it over to Git (I know Michael
prefers this) - whatever might help, just do it *now*.

Please help

          Andreas.

PS: Pablo, I would really prefer if you would communicate via the list
     because you always put me in danger to avoid netiquette.  Debian Med
     is much more than me and I'm not at all the educated imaging guy ...
--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Andreas Tille]

On Wed, 9 Jul 2008, Andreas Tille wrote:

> Please help

Michael,

on

    http://lists.debian.org/debian-med/2008/05/msg00064.html

you wrote:

    "So, please do not remove it!"

This explicite interest from your side lets me believe that you might
try to work on the patches because you might have to do it anyway when
you need CTN.  Could you please state explicitely whether my assumption
that you might work on this is right or wrong.  As I said I have nearly
no time but if I would know explicitely from our imaging experts that they
will not spend their time in working on the patch I might somehow try
this.  But I have not the slightest chance to test this stuff - I can
only see whether it compiles or not.

Please if you regard yourself as an medical imaging expert either try
to work on it or say explicitely "No, I can't do this for the moment."
This would be at least a clear information - just staying silent is
not helpful.

Kind regards

          Andreas.

--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Thijs Kinkhorst-4]

On Sun, July 13, 2008 18:25, Andreas Tille wrote:
> On Wed, 9 Jul 2008, Andreas Tille wrote:
>> Please help

I may be able to look at this during this week.

If that doesn't lead to anything useful, I'll file an RC bug against ctn.
Not to discourage anyone, but it is in my opinion in the *current* state
not releasable. Of course I would be more than welcome to someone updating
ctn's state and closing such bug.


Thijs


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Michael Hanke]

On Sun, Jul 13, 2008 at 06:25:49PM +0200, Andreas Tille wrote:

> On Wed, 9 Jul 2008, Andreas Tille wrote:
>
>> Please help
>
> Michael,
>
> on
>
>    http://lists.debian.org/debian-med/2008/05/msg00064.html
>
> you wrote:
>
>    "So, please do not remove it!"
>
> This explicite interest from your side lets me believe that you might
> try to work on the patches because you might have to do it anyway when
> you need CTN.  Could you please state explicitely whether my assumption
> that you might work on this is right or wrong.  As I said I have nearly
> no time but if I would know explicitely from our imaging experts that they
> will not spend their time in working on the patch I might somehow try
> this.  But I have not the slightest chance to test this stuff - I can
> only see whether it compiles or not.
>
> Please if you regard yourself as an medical imaging expert either try
> to work on it or say explicitely "No, I can't do this for the moment."
> This would be at least a clear information - just staying silent is
> not helpful.

You're right -- I'm sorry. I was following the discussion about CTN, but
I'm in the final phase of my PhD project and external forces reduce my
spare time dramatically. Additionally, I will be traveling from next
week till the middle of August and have to wrap some things up in
advance. But anyway, you're right that something has to be done.

IIRC the situation is this:

  * CTN mysql stuff is broken, since a long time. So, apparently those
    people who have it installed do not need it.
  * Nothing rdepends on ctn or ctn-dev, except for debian-med meta
    packages or ctn itself.
  * We know that at least dicomnifti and ctsim build-depend on ctn-dev.
    Is there a qick way (similar to `apt-cache rdepends ctn-dev`) to
    determines additional build-rdeps?
  * At least one individual offered to work on fixing the mysql stuff
    (don't have URL handy now, but it was posted recently).
  * Popcon ctn: approx. 120 since about one year (much less before)
           ctn-dev: just a few machines
  * CTN is dead upstream.

(please correct me if any of the above is wrong).

I have no clue what ctn as a whole can do and I have never touched the
database parts. If nobody else steps up, I'd offer to strip ctn down to
the pieces required by other packages (ctsim and dicomnifti). The will
probably lead to a minimal libctn-dev package.

Is this something we agree on?


Michael

--
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Andreas Tille]

On Mon, 14 Jul 2008, Michael Hanke wrote:

> You're right -- I'm sorry. I was following the discussion about CTN, but
> I'm in the final phase of my PhD project and external forces reduce my
> spare time dramatically.

Well, there is no need to soory, just finish your theses.  It might be
reasonable to issue a [VAC]-ation mail to keep people on this list informed
to let us know that we can not really count on you for a certain time span
so we do not need to ping you / wait for you.

> Additionally, I will be traveling from next
> week till the middle of August and have to wrap some things up in
> advance. But anyway, you're right that something has to be done.

Thijs offered to inspect Pablos patch which might probably be a quite
good solution ...

> IIRC the situation is this:
>
>  * CTN mysql stuff is broken, since a long time. So, apparently those
>    people who have it installed do not need it.

... and there is a patch available.

>  * Nothing rdepends on ctn or ctn-dev, except for debian-med meta
>    packages or ctn itself.

No, ctsim depends from it.

>  * We know that at least dicomnifti and ctsim build-depend on ctn-dev.
>    Is there a qick way (similar to `apt-cache rdepends ctn-dev`) to
>    determines additional build-rdeps?

Not that I know of - but imho the redepends of ctn are a good sign
for build-dependencies from ctn-dev.

>  * At least one individual offered to work on fixing the mysql stuff
>    (don't have URL handy now, but it was posted recently).

I just commited the patch to SVN.

>  * Popcon ctn: approx. 120 since about one year (much less before)
>           ctn-dev: just a few machines
>  * CTN is dead upstream.

We have several packages which are dead upstream ...

> I have no clue what ctn as a whole can do and I have never touched the
> database parts. If nobody else steps up, I'd offer to strip ctn down to
> the pieces required by other packages (ctsim and dicomnifti). The will
> probably lead to a minimal libctn-dev package.
>
> Is this something we agree on?

At least I think you should keep on your PhD work and we will be looking
foreward about your imaging work once you are back again ...

Kind regards

           Andreas.

--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Michael Hanke]

On Mon, Jul 14, 2008 at 11:33:46PM +0200, Andreas Tille wrote:

> On Mon, 14 Jul 2008, Michael Hanke wrote:
>
>> You're right -- I'm sorry. I was following the discussion about CTN, but
>> I'm in the final phase of my PhD project and external forces reduce my
>> spare time dramatically.
>
> Well, there is no need to soory, just finish your theses.  It might be
> reasonable to issue a [VAC]-ation mail to keep people on this list informed
> to let us know that we can not really count on you for a certain time span
> so we do not need to ping you / wait for you.

<snip>

> At least I think you should keep on your PhD work and we will be looking
> foreward about your imaging work once you are back again ...
;-) I hope it will not be like that (i.e. not boolean on/off).
Therefore, no VAC...


BTW: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421703

finally in NEW. If it makes it through, it will be a nice addition to
debian-med. Although, it might not make it into lenny -- but nice anyway
...


Cheers,

Michael






--
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[Andreas Tille]

On Tue, 15 Jul 2008, Michael Hanke wrote:

> BTW: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=421703
>
> finally in NEW. If it makes it through, it will be a nice addition to
> debian-med. Although, it might not make it into lenny -- but nice anyway
> ...

Great.  Thanks for your effort

         Andreas.

--
http://fam-tille.de


--
To UNSUBSCRIBE, email to debian-med-REQUEST@...
with a subject of "unsubscribe". Trouble? Contact listmaster@...

[smr99]

On Sun, Jul 13, 2008 at 06:25:49PM +0200, Andreas Tille wrote:

> Please if you regard yourself as an medical imaging expert either try
> to work on it or say explicitely "No, I can't do this for the moment."
> This would be at least a clear information - just staying silent is
> not helpful.

Well, "expert" puts the bar rather high, but since my name is on the
package as an uploader, let me say: "no, I won't be working on CTN
anytime soon".

In fact, I don't forsee that I will use or work on CTN ever.  So
whoever does modify it, please remove my name from uploaders.

Regards,
-Steve