On Thu, Nov 28, 2013 at 8:27 AM, Emmanuel Promayon <emmanuel.proma...@imag.fr> wrote: > Hi everyone, > >>> Furthermore I would like to mention another page[3] with lots of >>> information >>> about Debian Med packages. Besides the list of RC bugs you can also >>> see packages that can not be built on a Debian architecture, >>> packages that are not allowed to migrate from unstable to testing >>> (and thus won't be included in the next release) and packages with a >>> new upstream version. I think those packages need some care as well. >> >> >> +1 > > > I am trying to understand the mechanism of the "excuses" given for the > package CamiTK that is in the list of blocked packages in [1]. > As I am a very inexperienced in debian packaging, I am not sure what action > can be taken. > In the great page [2], the excuses for CamiTK point to a problem with > insightoolkit, which itself mention gdcm which now mention not yet built on > sparc and ia64 (which I suppose are the show stoppers). > But a while ago gdcm excuses were about the fact gdcm was part of a > transition (itself mentioning mono or something). > > What can be done concretely to fix this problem?
#730700 Thanks for the report ! -- To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/ca+7wusyqq8f5xw6b8qyrxwhrgyjbbvzuxe__6u28_jhz8jw...@mail.gmail.com
