[Debian-med-packaging] Removal of Slicer (Was: Bug#644352: python2.6 removal)

Dominique Belhachemi domibel at debian.org
Tue May 14 17:58:50 UTC 2013


Hi Andreas,

Don't worry. Only the outdated slicer3 will be removed.

Slicer4 integration is ongoing and looks good so far.

-Dominique


On Tue, May 14, 2013 at 1:20 PM, Andreas Tille <tille at debian.org> wrote:

> Hi Dominique,
>
> I have not checked the issue why slicer is FTBFS but I have the
> impression that the number of medical imaging experts in Debian Med team
> has grown.  As far as I understood the comment of Mathieu[1] he just has
> ignored this topic because of Wheezy release process.  I would call
> removal right now after Wheezy is released and some time resources might
> be freed for such problems as over-panicking.  May be delaying the
> removal some time might be reasonable.
>
> Kind regards
>
>       Andreas.
>
> On Mon, May 13, 2013 at 10:57:32PM -0400, Dominique Belhachemi wrote:
> > Hi Luca,
> >
> > Yes please, go ahead. I will add it back once it is buildable again.
> >
> > -Dominique
> > On May 13, 2013 10:54 AM, "Luca Falavigna" <dktrkranz at debian.org> wrote:
> >
> > > Hi Dominique!
> > >
> > > slicer3 is one of the packages needed to be rebuilt to get rid of
> > > python2.6 dependencies. As it currently FTBFS, I wonder whether it
> > > would be better to remove it from unstable.
> > >
>
> [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655822#12
>
> --
> http://fam-tille.de
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20130514/17b50f6e/attachment.html>


More information about the Debian-med-packaging mailing list