Re: Python package review
Hi Sascha, I just noticed that I did not properly checked the package which does not follow our group policy regarding Maintainer / Uploader: Index: control === --- control (Revision 12997) +++ control (Arbeitskopie) @@ -1,7 +1,8 @@ Source: genometools Section: science Priority: optional -Maintainer: Sascha Steinbiss +Maintainer: Debian Med Packaging Team +Uploaders: Sascha Steinbiss Build-Depends: debhelper (>= 9), liblua5.1-0-dev, liblua5.1-md5-dev, liblua5.1-filesystem-dev, liblua5.1-lpeg-dev, libcairo2-dev, zlib1g-dev, libbz2-dev, libexpat1-dev, I just realised that the notification mail did not went to our mailing list. There are a lot of good reasons to set the mailing list as the maintainer - only one of them is that we would have noticed the rejection you faced yesterday on your own at the same time and could have reacted earlier. So it would be great if you would apply the patch above for better handling in the future. Kind regards Andreas. -- http://fam-tille.de -- 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/20130213081219.ga10...@an3as.eu
itk and tiff
Ok, so itk is failing to build on big endian systems because of the TIFF that is included with itk. I fixed this before, but it has come back. I sent a patch upstream [1], and it has been merged and will probably be in the next release. However, we should probably use the system TIFF. The reason we didn't before was because it "requires version 4, but libvtk5-dev depends on version 3" according to the notes in the rules file. But as far as I can tell, libvtk5 no longer uses version 3. There is a bug in itk when you enable system tiff, but I have attached a patch and submitted it upstream [2]. With the patch, itk builds and passes all the tests on my machine (amd64). So, long story short, we should use system tiff (-DITK_USE_SYSTEM_TIFF:BOOL=ON) and apply the attached patch. Or, not use system tiff and use the patch in [1]. I vote for using system tiff. -Paul [1] http://review.source.kitware.com/9382 [2] http://review.source.kitware.com/9798 --- insighttoolkit4-4.3.1.orig/Modules/Compatibility/Deprecated/test/itkTestDriverIncludeDeprecatedIOFactories.h +++ insighttoolkit4-4.3.1/Modules/Compatibility/Deprecated/test/itkTestDriverIncludeDeprecatedIOFactories.h @@ -23,7 +23,10 @@ #include "itkNiftiImageIOFactory.h" #include "itkGiplImageIOFactory.h" #include "itkJPEGImageIOFactory.h" -#include "itkLSMImageIOFactory.h" +#include "itk_tiff.h" // ITK_USE_SYSTEM_TIFF +#ifndef ITK_USE_SYSTEM_TIFF +# include "itkLSMImageIOFactory.h" +#endif // ITK_USE_SYSTEM_TIFF #include "itkMetaImageIOFactory.h" #include "itkPNGImageIOFactory.h" #include "itkNrrdImageIOFactory.h" @@ -43,7 +46,9 @@ itk::ObjectFactoryBase::RegisterFactory( itk::PNGImageIOFactory::New() ); itk::ObjectFactoryBase::RegisterFactory( itk::VTKImageIOFactory::New() ); itk::ObjectFactoryBase::RegisterFactory( itk::GiplImageIOFactory::New() ); +#ifndef ITK_USE_SYSTEM_TIFF itk::ObjectFactoryBase::RegisterFactory( itk::LSMImageIOFactory::New() ); +#endif // ITK_USE_SYSTEM_TIFF itk::ObjectFactoryBase::RegisterFactory( itk::NiftiImageIOFactory::New() ); itk::ObjectFactoryBase::RegisterFactory( itk::JPEGImageIOFactory::New() ); itk::ObjectFactoryBase::RegisterFactory( itk::TIFFImageIOFactory::New() );
Just read an article about cloud tools for Debian
Hi, for those who might be interested: http://julien.danjou.info/blog/2013/cloud-init-utils-debian Kind regards Andreas. -- http://fam-tille.de -- 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/20130213150246.ga18...@an3as.eu
Re: [MoM] Debian Med MoM for February
Hi Andreas, Andreas Tille wrote: >0.0.20080513 > > (because this is the change date of the youngest file > README_en_MED.txt.) BTW, the response time of upstream is frequently > related to the time difference between today and their last release - > so I would not expect any soonish answer and we should try to proceed > even without any response. In that case, I have to rename the pristine-tar ... how do I go about doing that or should I start afresh? (I tried searching but I can't find anything). -- Sukhbir -- 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/20130213181920.ga3...@gmail.com
Re: [MoM] Debian Med MoM for February
> > (because this is the change date of the youngest file > > README_en_MED.txt.) BTW, the response time of upstream is frequently > > related to the time difference between today and their last release - > > so I would not expect any soonish answer and we should try to proceed > > even without any response. > > In that case, I have to rename the pristine-tar ... how do I go > about doing that or should I start afresh? (I tried searching but I > can't find anything). By this I mean, that renaming the package will mess up (?) the original `git import-orig'. -- Sukhbir -- 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/20130213185228.gb3...@gmail.com
Re: [MoM] Debian Med MoM for February
On Wed, Feb 13, 2013 at 01:52:28PM -0500, Sukhbir Singh wrote: > > In that case, I have to rename the pristine-tar ... how do I go > > about doing that or should I start afresh? (I tried searching but I > > can't find anything). > > By this I mean, that renaming the package will mess up (?) the original > `git import-orig'. The simplest and most appropriate (considering there is basically no history) solution is in fact to create the Git repository from scratch. Kind regards Andreas. -- http://fam-tille.de -- 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/20130213191205.gc18...@an3as.eu
My Debian Med talks at FOSDEM
Hi, I wrote a short Blog article in Debian Med blog about my talks at FOSDEM including links to the slides and the video recording of the Cross Distro talk. http://debianmed.blogspot.de/2013/02/debian-med-talk-at-fosdem-by-andreas.html Thanks to all the team member who made this possible Andreas. -- http://fam-tille.de -- 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/20130213195732.ge18...@an3as.eu
Re: [MoM] Debian Med MoM for February
Hi Andreas, Andreas Tille wrote: > The simplest and most appropriate (considering there is basically no > history) solution is in fact to create the Git repository from scratch. I just rebuilt the repository and made the changes. `lintian' output is clean but the issue with the watch file still remains. Please have a look! -- Sukhbir -- 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/20130213235627.gd3...@gmail.com
