Bits from Debian Med team (by Andreas Tille)

New set of metapackages

The version number of debian-med metapackages was bumped to 1.99 as a signal that we plan to release version 2.0 with Jessie. As usual the metapackages will be recreated shortly before the final release to include potential changes in the package pool. Feel free to install the metapackages med-* with the package installer of your choice.

As always you can have a look at the packages in our focus by visiting our tasks pages. Please note that there may be new packages that aren’t ready for release and that won’t be installed by using the current metapackages. This is because we don’t stop packaging software when the current testing is in freeze.

Some support for Hospital Information Systems

This release contains, for the first time some support for Hospital Information Systems (HIS) with the dependency fis-gtm of the med-his metapackage. This was made possible due to the work of Luis Ibanez (at kitware at the time when working on the packaging) and Amul Shah (fisglobal). Thanks to a fruitful cooperation between upstream FIS and Debian the build system of fis-gtm was adapted to enable an easier packaging.

The availability of fis-gtm will simplify running Vista-foia on Debian systems and we are finally working on packaging Vista as well to make Debian fit for running inside hospitals.

There was some interesting work done by Emilien Klein who was working hard to get GNUHealth packaged. Emilien has given a detailed explanation on the Debian Med mailing list giving reasons why he removed the existing packages from the Debian package pool again. While this is a shame for GNUHealth users there might be an opportunity to revive this effort if there was better coordination between upstream and Tryton (which is the framework GNUHealth is based upon). In any case the packaging code in SVN as a useful resource to base private packages on. Feel free to contact us via the Debian Med mailing list if you consider creating GNUHealth Debian packages.

Packages moved from non-free to main

The Debian Med team worked hard to finally enable DFSG free licenses for PHYLIP and other package based on this tool. PHYLIP is well known in bioinformatics and actually one of the first packages in this field inside Debian (oldest changelog entry 28 Aug 1998). Since then it was considered non-free because its use was restricted to scientific / non-commercial use and also has the condition that you need to pay a fee to the University of Washington if you intend to use it commercially.

Since Debian Med was started we were in continuous discussion with the author Joe Felsenstein. We even started an online petition to show how large the interest in a DFSG free PHYLIP might be. As a side note: This petition was *not* presented to the authors since they happily decided to move to a free license because of previous discussion and since they realised that the money they "gained" over they years was only minimal. The petition is mentioned here to demonstrate that it is possible to gather support to see positive changes implemented that benefit all users and that this approach can be used for similar cases.

So finally PHYLIP was released in September under a BSD-2-clause license and in turn SeaView (a similarly famous program and also long term non-free citizen) depending on PHYLIP code was freed as well. There are several other tools like python-biopython and python-cogent which are calling PHYLIP if it exists. So not only is PHYLIP freed we can now stop removing those parts of the test suites of these other tools that are using PHYLIP.

Thanks to all who participated in freeing PHYLIP specifically its author Joe Felsenstein.

Autopkgtest in Debian Med packages

We tried hard to add autopkgtests to all packages where some upstream test suite exists and we also tried to create some tests on our own. Since we consider testing of scientific software a very important feature this work was highly focused on for the Jessie release. When doing so we were able to drastically enhance the reliability of packages and found new formerly hidden dependency relations. Perhaps the hardest work was to run the full test suite of python-biopython which also has uncovered some hidden bugs in the upstream code on architectures that are not so frequently used in the field of bioinformatics. This was made possible by the very good support of upstream who were very helpful in solving the issues we reported.

However, we are not at 100% coverage of autopkgtest and we will keep on working on our packages in the next release cycle for Jessie+1.

General quality assurance

A general inspection of all Debian Med packages was done to check all packages which were uploaded before the Wheezy release and never touched since then. Those packages where checked for changed upstream locations which might have been hidden from uscan and in some cases new upstream releases were spotted by doing this investigation. Other old packages were re-uploaded conforming to current policy and packaging tools also polishing lintian issues.

Publication with Debian Med involvement

The Debian Med team is involved in a paper which is in BioMed Central (in press). The title will be "Community-driven development for computational biology at Sprints, Hackathons and Codefests"

Updated team metrics

The team metrics graphs on the Debian Med Blend entry page were updated. At the bottom you will find a 3D Bar chart of dependencies of selected metapackages over different versions. It shows our continuous work in several fields. Thanks to all Debian Med team members for their rigorous work on our common goal to make Debian the best operating system for medicine and biology.

Please note that VCS stat calculation is currently broken and does not reflect the latest commits this year.

Blends installable via d-i?

In bug #758116 it is requested to list all Blends and thus also Debian Med in the initial tasksel selection. This would solve a long term open issue which was addessed more than eleven years ago (in #186085) in a more general and better way. This would add a frequently requested feature by our users who always wonder how to install Debian Med.

While there is no final decision on bug #758116 and we are quite late with the request to get this implemented in Jessie feel free to contribute ideas so that this selection of Blends can be done in the best possible manner.

Debian Med Bug Squashing Advent Calendar 2014

The Debian Med team will again do the Bug Squashing Advent Calendar. Feel free to join us in our bug squashing effort where we close bugs while other people are opening doors. :-)

Bits from Debian Med team (by Andreas Tille)

Some of these bits are a bit outdated but there is no point in hiding this information just because it is old.

FOSDEM talk

Andreas Tille had a talk at FOSDEM which is also Video recorded. A quite similar but updated talk was held at DebConf 13 (see below).

Jabber interview by reporter from India

There was an interesting interview between Rajeev Nair and Andreas Tille at So, 17.02.2013 Rajeev Nair is Business head of an health care journal in India held via jabber. Since this might serve as some nice FAQ about Debian Med here is a complete log of this interview (permission to publish it was granted).

Article about Debian Med

As a consequence of the interview above the Debian Med team has assembled an article which was originally intended to be published in the Health Cafe journal but somehow this never happened. So we ended up with a nice article targeting at interested readers about Free Software in medicine with not necessarily informatics background. Since the article is considered to be of good quality and has consumed some time of several team members we are seeking for ideas for relevant places where to publish it. It is available as PDF as well as in SVN.

Yearly sprint of Debian Med team

This year we had our third sprint of the Debian Med team and all participants consider it a great success again. The sprint was in end of February and the individual reports are linked from the according wiki page. Since Andreas Tille was able to prove the nice effect of having face to face meetings in Debian teams in the team metrics graphs presented in his talks at DebConf (see below) we will keep on with this good tradition. The next sprint is scheduled for Friday 31st January until Sunday 2nd February in Stonehaven near Aberdeen. If you are interested to meet the people behind Debian Med and want to join us in developing packages which are helpful in health care and bioinformatics you are invited to join us.

DebConf 13 in Vaumarcus

Andreas Tille had two talks with specific influence to Debian Med development(Debian Med as a success story for other Blends, How to attract new developers for your team (MoM, SoB). For those who want to read a full (and lengthy) report about DebConf 13 by Andreas Tille this is online in this blog article.

Codefest of the Open Bioinformatics Foundation

Ivo Maintz and Steffen Möller organised the Codefest of the Open Bioinformatics Foundation in Berlin. About 40 contributors from all over the world attended, connecting the Debian community strongly with upstream. The event triggered a joint paper of participants to Sprints, Codefests and Hackathons alike, presented at the Nettab conference on Semantic, Social, and Mobile Applications for Bioinformatics and Biomedical Laboratories in Venice.

Reupload unattended packages

Andreas Tille has mentored the GSoC student Emmanouil Kiagias and as a byproduct some Blends metadata were now kept in UDD. This has inspired some new tools and one of this was an UDD query to return all packages in the interest of the Blend ordered by date when they were uploaded. It has shown that there were packages hanging around in the package pool since five years. So some effort was done to check those packages which were not necessarily "buggy" according to BTS entries and so we were able to fix the following issues in about 20-30 packages:

• Remove DM-Upload-Allowed fields
• hardening
• canonical Vcs fields
• checking homepages / watch files
• checking policy 3.9.4 (cme fix dpkg-control)
• profit from xz compression in binary packages which makes perfectly sense in some of our packages
• DEP5
• DEP3
• use dh consequently to simplify things for team members / NMUers
• finally upload several changes in VCS but remained UNRELEASED
• found several other hidden issues like

Since it was impressive how many things that deserve fixing are hidden in such long unattended packages it is recommended also to other teams to spend some time into these. The UDD query can be easily tweaked for a team maintainer address.

Debian Med Bug Squashing Advent Calendar 2013

The Debian Med team will again do the Bug Squashing Advent Calendar. Feel free to join us in our bug squashing effort where we close bugs while other people are opening doors. :-)

Kind regards and see you at Debian Med sprint
Andreas.

DebConf 13 report (by Andreas Tille)

General impression

I'm beginning my DebConf report in an unofficial "Scenic Hacklab" right at the edge of the lake in Yverdon. This is the right place to memorise the last days. When I started from this place cycling to Le Camp 12 days ago I was full of great expectations and what should I say - the reality has even beaten these.

Once it comes about comparing DebConfs even if it is an unfair comparison due all the differences my secret long term favourite was Helsinki very closely followed by Argentina and also very closely followed by all the other great DebConfs I joined (and I joined all in Europe). Would Le Camp be able to beat it? The short answer is: Yes, it is now my favourite DebConf while I think I do not suffer from the last-Debconf-was-the-best-DebConf-syndrome (and I realised there are others thinking the same).

As you might probably know I'm a bit addicted to swimming. While Helsinki had admittedly the better conditions I was at least able to fix the distance issue using my bicycle. (Hey, those Le Camp photographers did a great job in hiding the fact that you can not actually touch the lake right from the meadow of Le Camp.) Being able to have my bicycle at DebConf scored some extra points. However, the really great view of the lake, the inspiring "Scenic Hacklab" which was my favourite place has bumped DebConf13 at first place in my personal ranking.

So it comes quite natural to say: "Kudos to the great organisation team!" They did a Swiss-like precise work and perfectly succeeded in hiding any problems (I assume there were some as always) from the attendees so everything went smooth, nice and shiny for the attendees. The local team was even precise in setting up great weather conditions for DebConf.

While saying thanks to the local team I would like to also explicitly thank Luca Capello who has quite some share that this DebConf was possible at all (while I have to decrease my DebConf score one point because he was not really there - Luca to bad that you were not able to come full time!) Also thanks to Gunnar and Gannef who helped remotely (another score down because I were missing them this year as well).

Even if it was my favourite DebConf I was not able to work down my todo list fully (which was not only uploading one package per day which I at least statistically fullfilled). But that's probably a general feature of todo lists anyway. One item was definitely done: Doing my daily swimming BoF. I actually was able to do the other parts of the triathlon which was skipped by Christian and have done in summary about 150km cycling with 3500m elevation and estimated 7-8km swimming (0m elevation ;-)). Considering the great view at sunrise over the lake I was not hating my "Senile bed escape" disease too much (I was every day waking up at sunset) - it was simply a great experience. I will never forget seeing water drips glimmering like gold inside the morning sun while seeing the Alps panorama in the distant. I hope I was able to help all interested swimmers with the DebConf Beach Map which was just a by-product of my activities in DebCamp.

Speaking about OSM: I was astonished that the area was way less covered than I expected. Thanks to several DebConf attendees the situation became better and the map does not only show random trees in the wild but also the tracks leading to these. (Remark: It was no DebConf attendee who is responsible for plastering the map with single trees.) While I had my mapping focus basically close to the edge of the lake I was also able to even map my very own street. :-)

I clearly remember one specific mapping tour when I was invited by the DPL: He convinced me to join him on a bicycle tour and since I was afraid to get fired I joined him instead to keep on hacking. Also Sorina was brave enough to join us on the tour and she did quite well. (Sorina, do you remember the agreement about your work on the installer? ;-)) Lucas described the tour as: going uphill on only asphalted roads. Sorina and me were witnessing the mighty DPL powers when we left the wood around Le Camp to reach the described road: The asphalt was just put onto the road - no doubt that it was done on the immediate demand of mighty DPL. :-)

DebCamp time was flying like nose dive and a lot of known (and unknown) faces arrived at Le Camp. What I really liked a lot this year was that several really young children has pulled down the average age of DebConf attendees. I clearly remember all the discussion one year ago what to do about children. As always the issue was solved in a typical Debian way: Just do it and bring your children - they had obviously a great time as well. I think the youngest child was 2 months and the oldest "child" above 20. ;-) Actually Baptiste Perrier did great in making the C&W party a success and had obviously a nice time. (I wished my son would have been able to come as well but he needs to write his bachelor’s thesis in physics. :-()

It was nice to see the kids using all playing facilities and communicating with geeks. Also I would like to point out that even the very young attendees had their share at the success of DebConf: Just think of the three "bell ringing assistants" who helped me ringing the bells for lunch and dinner. I've got this cool job from Didier in the beginning of DebCamp. I must say having some real bells ringing is by far nicer than just the "lunch / dinner starts in 10 minutes" from IRC bot. The only thing I did not understand was that people did not considered ringing the bells at 8:00 for breakfast as a good idea.

Regarding the food in general I would also like to send kudos to the kitchen: It was tasty, freshly prepared, regional food with a good change rate. I really liked this. Extra points for having the chance to sit outside when eating.

Talks

But lets have a look into the conference programme. I'd really recommend watching the videos of the talks Bits from the DPL (video) and Debian Cosmology (video). I considered both talks as entertaining and interesting. I also really hope that the effort Enrico Zini started in Debian Contributors (video) will be successful.

I had some talks and BoFs myself starting with Why running a Blend (video) and I admit that (as usual) the number of attendees was quite low even if I think there is some proof (see below) that it is interesting for way more people who should consider working more "blendish" in their team. Do you know how to recruit one developer per year and relax the man power problem in your team? Feel free to watch the video. We have confirmation that ten DDs of our team have considered to join Debian only because Debian Med exists. Admittedly biology and medicine are really leaf topics inside the Debian universe. So if even this topic that has a very tiny share of the Debian users is able to attract this level of attention - how many more people could we win for multimedia, games, GIS and others?

So if you feel you are quite overworked with your packaging and you have no time this is most probably wrong. The amount of time is basically a matter of priorities you set for your tasks. Try to put some higher priority onto using the just existing Blends tools I explained in my talk to attract more users and developers to your team and by doing so spread the workload over more people. It works, the prove was given in my main talk. So before you start working on a specific package you should wonder who else could have an even stronger interest to get this work done and provide him with some additional motivation and help to get the common goal done.

The interesting thing is that my BoF about How to attract new developers for your team (video) - which was a simple report about some by-product of the Blends work - made it into the main talk room and got way more attention. For me this is the proof that the Blends concept itself is probably badly perceived as something like "a few outsiders are doing damn specific stuff which is not really interesting for anybody else" instead of what is really is: Smoothing the way from specific upstream applications to the end user via Debian.

Once you see the video of this BoF you can observe how my friend Asheesh Laroia became more and more excited about the Blends concept and admitted what I said above: We should have more Blends for different fields. Funnily enough Asheesh asked me in his excitement to talk more about Blends. This would have been a really good suggestion ten years ago. At DebConf 3 in Oslo I had my very first talk about Blends (at this time under the name "Debian Internal Projects"). I continuously kept on talking about this (MiniDebConf Peking 2005, DebConf 5, Helsinki (video), DebConf 7, Edinburgh (video), DebConf 8, Mar del Plata (video), DebConf 9, Cáceres (video), MiniDebConf Berlin 2010 (video in German), MiniDebConf Paris 2010 (not video recorded), DebConf 11, Banja Luka (video) ... and these are only (Mini)DebConfs my talks page is full of this topic) and every new year I try different ways to communicate the idea to my fellow Debianistas. I'm wondering how I could invent a title + abstract avoiding the term Blends, put "Git", "release" and "systemd versus upstart" in and being able to inform about Blends reasonably by not becoming to off topic with the abstract.

I also registered the Debian Science round table. I admit we were lacking some input from remote via IRC which used to be quite helpful in the past. The attendees agreed upon the handling of citations in debian/upstream files which was invented by Debian Med team to create even stronger bounds to our upstream developers by giving their work extra reward and providing users with even better documentation (see my summary in Wiki). As usual I suggested to create some Debian Science offsprings like "Debian Astronomy", "Debian Electronics", "Debian Mathematics", "Debian Physics" etc. who could perfectly leave the Debian Science umbrella to get a more fine grained structure and a more focused team to enhance the contact to our users. Unfortunately there is nobody who volunteers to take over the lead for such Blends. I have given a short summary about this BoF on the Debian Science mailing list.

In the Debian Med meeting I have given some status report. No other long term team members were attending DebConf and so I gave some kind of introduction for newcomers and interested people. I touched also the DebiChem topic which maintains some packages that are used by biologists frequently and so we have a good connection to this team.

Finally I had registered three BoFs in Blends I'm actually not (or not yet) active part of. My motivation was to turn the ideas I have explained in my main talk into specific application inside these teams and helping them to implement the Blends framework.

In the first BoF about Debian GIS I have shown the usual team metrics graphs to demonstrate, that the one packaging team Pkg-OSM is in danger to become MIA. There are only three persons doing actual uploads. Two of them were at DebConf but did not joined the BoF because they do not consider their contribution to Pkg-OSM as a major part of their general Debian work. I will contact the main contributor David Paleino about his opinion to move the packages step by step into maintenance of Debian GIS packaging team to try to overcome the split of two teams that are sharing a good amount of interest. At least if I might become an Uploader for one of the packages currently maintained by Pkg-OSM I will move this to pkg-grass-devel (which is the name of the packaging team of Debian GIS for historical reasons). The attendees of the BoF have considered this plan as sensible.

Moreover I talked about my experiences with OSGeo Live - an Ubuntu derivative that tries to provide a full tool chain to work on GIS and OSM problems ... basically the same goal as Debian GIS has just provided by the OSGeo project. I'm lurking on OSGeo mailing list when I asked explicitly I've got the answer that they are working together with Debian GIS and are using common repository (which is IMHO the optimal way of cooperation). However, it seems that several protagonists of OSGeo Live are underestimating the resources provided by Debian. For instance there was a question about Java packaging issues but people were not aware about the existence of the debian-java mailing list. I was able to give an example how the Debian Med team managed to strengthen its ties to BioLinux that is also an Ubuntu derivative for biologists. At our first Debian Med sprint in 2011 we invited developers from BioLinux and reached a state where they are using the very same VCS on Alioth where we are maintaining our packages. At DebConf I was able to upload two packages where BioLinux developers did certain changes for enhancing the user experience. My "work" was just bumping the version number in changelog and so we did profit from the work of the BioLinux developers as well as they are profiting from our work. I plan to dive a bit more into Debian GIS and try to strengthen the connection to OSGeo Live a bit.

The next BoF was the Debian Multimedia meeting. It was nice that the current leader of Ubuntu Studio Kaj Ailomaa joined the meeting. When I was explaining my ideas about cooperation with derivatives I repeated my detailed explanation about the relation with BioLinux. It seems every topic you could cover inside Debian has its related derivative. So to me it seems to be quite natural to work together with the developers of the derivative to join forces. I actually consider a Blend a derivative done the right way = inside Debian. The final work for the derivers that might be left for them is doing some shiny customising of backgrounds or something like this - but all the hard work could and should be done in common with the relevant Debian team. My dream is to raise such relevant teams inside Debian ... the Blends.

Finally the last BoF of this series was the Debian Games meeting. As always I presented the team metrics graphs and the Debian Games team members who attended the BoF were quite interested. So it seems to be some unknown fact that team metrics are done for several teams in side Debian and so I repeat the link to it for those who are not yet aware of it. As a result of the BoF Debian Games team members agreed to put some more effort into maintaining their Blends tasks. Moreover Miriam Ruiz wants to put some effort into reviving Debian Jr. Regarding Debian Jr. there was an interesting talk about DouDouLinux - in case you might want to watch the video I'd recommend skipping the first 30min and rather watch the nice live demo. There was also an ad hoc BoF about Debian Jr scheduled to bring together all people interested into this cute project and Per Anderson volunteered to take over the lead. I have given a summary about this specific BoF at the Debian Jr list.

For some other talks that I'd regard as remarkable for some reasons: I'd regard the talk "Debian-LAN" by Andreas Mundt as some hidden pearl because it did not got a lot of attention but after having seen the video I was quite impressed - specifically because it is also relevant for the Blends topic.

Memories

I also liked "Paths into Debian" by Moray Allan (and I was only able to enjoy the latter talks thanks to the great work of the video team!) because it also scratched the same topic I was concerned about in my mentoring talk. Related to this was in my opinion also "Women in Debian 2013" were we tried to find out reasons for the lack of woman compared to other projects and how to overcome this issue.

Besides the talks I will probably never forget two specific moments that make DebConf so special. One of these moments is recorded on an image that clearly needs no words - just see Geert hovering over the grass.

Another strong moment in my personal record was in the DebConf Newbies BoF "First time at DebConf" that unfortunately was not recorded but at least for this statement it would have been very great if we would have some reference better than personal memory. Aarsh Shah a GSoC student from India suddenly raised up and said: "Four months ago I was not even aware that Free Software exists. Now I'm here with so many people who are totally equal. If I will tell my mother at home that I was standing in the same queue where the Debian Project Leader was queuing up for food she will never believe me." He was totally excited about things we are regarding as normal. IMHO we should memorise moments like this that might be part of the key to success in cultures, where Debian is widely unknown and very rarely in use.

Amongst these not scheduled great moments the scheduled day trip was also a great thing. I had a really hard time to decide what tour I might join but ended up in the "long distance walking (or should I say running) group". Inspired by the "running Bubulle" who was flashing between the walking groups we went uphill with 5.4km/h which was a nice exercise. Our destination the large cliff was an exciting landscape and I guess we all enjoyed the dinner organised by the "Trout cabal". ;-)

So I had a hard time to leave Le Camp and tried hard to make sure my memories will remain as long as possible. Keeping some signs attached to my bicycle, conserving the "Scenic Hacklab" sign for my private "scenic hacklab @ home" was one part. I also have cut some branches of the Buxus sempervirens in Le Camp and have put them in my garden at home (where I create some hedgerow from places where I spent some great time). These will probably build a great part of the hedgerow ...

Thanks for reading this longish report.

Looking forward to see you all in Germany 2015 (or earlier) Andreas.

Debian Med sprint report (by Andreas Tille)

This is the report about my work at Debian Med sprint ten days ago in Schönberger Strand. If you are interested in Sprints in general you might be interested in work item 2. below.

1. Wrote draft article for Indian health care magazin. If you might like to proofread the article I'd be very happy (it is not yet to late for changes.) There is also a PDF version.
2. I have given a short talk proving the importance of sprints. The slides are basically graphs and I try to prove that sprints are a really good idea. The background knowledge is that the Debian Med team is doing sprints since 2011 and looking at all graphs you can see that this has a really positive effect. Thanks to Debian and its sponsors for supporting this kind of sprints.
3. Packaging
   • Worked with T. Travis on flexbar and uploaded the package to new queue
   • Worked with Ch. Gille on strap-base and uploaded the package to new queue
   • Discussed strategy how to strip glam2 source from meme upstream with T. Booth. Meme upstream agreed to keep the original license of Glam2 and backport the changes from Meme source archive
   • Discussed igv packaging issues with O. Sallou who updated the package and documented some issues about its dependency goby
   • Worked together with I. Maintz on cellprofiler
   • Worked together with I. Maintz on a couple of R packages which are mostly predependencies but also one Debian Med primary target (r-cran-boolnet) was uploaded to new
4. Discussing / chatting
   • Some chat with Ch. Steigies (Debian Games, Debian m68k, Debian Science)
   • Discussion with M. Banck about DebiChem
5. Little bit of MoM mentoring
6. Maintain Debian Med tasks files about newly commited packages of other sprint participants
7. General infrastucture issues
   • Issues with machine-readable files importer into UDD
   • Try to revive PET data in UDD
   • Work on installation of future blends.debian.net host (install needed packages, create UDD clone)

Thanks to all participants of the sprint and specifically to Steffen Möller who took over the work of organising. It was fun to meet you all and I'm even looking right now forward to the next sprint hopefully beeing able to continue the graphing of positive results of sprints in our team metrics.
We had some nice food, not so nice weather and from my perspective the only drawback was that at home there would have been perfect conditions for skiing ... but finally there are preferences. ;-)
See you at next sprint!

Debian Med talk at FOSDEM (by Andreas Tille)

At FOSDEM I was talking even two times about Debian Med.  The talk in the morning was attached to the FOSS for scientists track and was only a short overview about the use scientists can make from Debian Med.  As usual the slides are available from my web page.
The main talk was in the evening in the Cross Distro Devroom and it was even video recorded.
It was fun to be at FOSDEM for the first time and meet a lot of Debian people and discuss new ideas with them.

Bits from Debian Med team (Posted by Andreas Tille)

This are the new years bits from Debian Med team. We try to make the wishes for a healthy new year becoming true with Free Software. :-)

Debian Med Bug Squashing Advent Calendar 2012

As last year the Debian Med team did some advent calendar bug squashing. The summary states 15 bugs from Debian Med scope which is less than last year but Debian Med team members also did some general bug squashing to help the Wheezy release. Finally this makes a lot of sense also for Debian Med if we can speed up the release. When counting the additional 12 RC bugs fixed in the advent calendar effort we again managed to fix more than one bug per day. Please keep on squashing RC bugs for Wheezy!

Mentoring of Month

Last year Andreas Tille started the Mentoring of Month effort to lower the entrance barrier for newcomers. There was no student for every month and not each package was uploaded at end of month but expecting such a high number of newcomers would be unrealistic anyway. So I'd like to draw some positive conclusion that we now have some newcomers friendly invited to the project and some packages uploaded or at least prepared which would not be there without the MoM project. Finally all MoM students liked the project and we will continue it in the future and would like to recommend other teams to do something similar.

Planed Debian Med sprint in Kiel

The next Debian Med sprint for real life meeting of Debian Med developers and users will happen in Kiel 23rd/24th of February. All interested people are invited to join to continue the success of the past two sprints. We are currently in the planing phase but there are just some hot topics which are workflows, licensing (specifically bug #694908), cooperation with Ubuntu and BioLinux and other things.

Metapackages targeting at Wheezy

Currently Debian Med metapackages version 1.13.2 are in unstable and once the unblock request is accepted by Debian release team this version will target at Wheezy. This means your very last chance to influence the metapackage content regarding some missing dependencies is defacto over now. Please closely observe our web sentinel in case you are interested in the work of Debian Med and tell us if packages are missing from our focus.

Kind regards and see you at Debian Med sprint
   Andreas.

Debian Med Bits: Report from LSM Geneva by Andreas Tille

In this report from LSM 2012 in Geneva I will report about

1. Medical imaging using Debian
2. Debian Med packaging workshop
3. Integration of VistA into Debian
4. Other interesting talks

Medical imaging using Debian

There were about 10 attendees basically upstream developers of medical imaging software.  The talk got some attention and the message to include even more medical imaging software into Debian was well percived.  Thanks to Mathieu Malaterre there was some live demonstration which was way easier for him as a medical imaging expert than it would have been for me.

Debian Med packaging workshop

Due to my advertising in the talk yesterday three students (two of them from one medical imaging project, one from an other project) attended the workshop.  Thanks to Axel Beckert who helped me out surviving the challenge to walk on unexplored ground.

The idea of the workshop was to ask the attendees to name a package of their own and just package this.  Because two of the attendees were upstream developers of CreaTools we decided to go on for packaging this.  After circumeventing some pitfalls in the beginning it went rather smoothly and after about 2.5 hours we were able to commit some initial packaging to the Debian Med Git repository which comes quite close to a ready package (perhaps some split into a library and a development package needs to be done and for sure testing is needed).
Quoting Frederic Cervenansky, upstream of CreaTools

Thanks for your work. Your workshop was very interesting and didactic: a relevant discussion between Claire and me for the future of Creatools has emerged from the difficulties you  encountered to package creatools. I will try, before the end of the month, to fully package creatools. And for sure, I will contact the debian-med mailing list.

Integration of VistA into Debian

I had the good chance to directly address some issues of Claudio Zaugg the speaker in the talk Implementing open source Health Information Systems in Low- and Middle Income Countries – a practical review directly before mine.  It turned out that by using Debian packaged software might help simplifying the issues they had in supporting health care workers in Low- and Middle Income Countries.
My talk was partly repeating some basic ideas about Debian Med from the talk on Monday because the audience was completely different.  Than I tried to explain in detail how we tried hard to establish good contacts to upstream developers and why this is essential to finalise the goal to include hospital information systems straight into Debian any by doing so open the doors of hospitals for large scale Debian installations.
There is also video recording of this talk.

Other interesting talks

OpenEMR, a multi-language free open source electronic health record for international use

Just discussed the packaging of OpenEMR which is prepared for Debian Med as it can be seen on our tasks page.  The contact to the creator of some inofficial package will be established to finalise this task.

OpenFovea : when open-source and biophysical research get married

Just another target for Debian Med popped up in this talk to further enhance Debian Med in covering all issues of medical care on one hand and on the other hand helping upstream authors to distribute their code
more effectively.

Collaborative software development for nanoscale physics

The talk would have fit very nicely into the Debian Science workshop at ESRF (European Synchrotron Radiation Facility) in Grenoble because it was about ETRF (European Theoretical Radiation Facility).  At previous LSM events I had just talked with Yann and the work to include their software into Debian is on its way.

Free software and High Performance Computing

This talk was not directly connected to my Debian work but I simply enjoyed to see how "two people" had a really entertaining talk about Top 500 computers.  Vittoria, you made my last day at LSM.

New Debian Med metapackages uploaded (Posted by Andreas Tille)

I just uploaded new metapackages featuring dependencies of several new packages prepared thanks to the great work of the Debian Med team. Here are the newcomers (and packages we lost):

med-bio:
+ ballview
+ bowtie2
+ cd-hit
+ clustalo
+ ffindex
+ gassst
+ grinder
+ hhsuite
+ profphd-utils
+ proftmb
+ profphd
+ profphd-utils
+ pynast
+ qiime
+ r-bioc-cummerbund
+ reprof
- seq-gen (turned out to be non-free)

med-bio-dev:
+ libchado-perl
+ libffindex0-dev
+ libtfbs-perl
+ libpal-java
+ librg-reprof-bundle-perl
+ librostlab-blast0-dev
+ librostlab-blast-doc
+ librostlab3-dev
+ librostlab-doc
+ libzerg0-dev
+ libzerg-perl

med-data:
- freediams (restructuring upstream, will be back with next release hopefully)

med-imaging:
+ imagevis3d
+ itksnap
+ odin
+ volview

med-imaging-dev:
+ python-pyxnat

med-practice:
+ clinica
- freediams (restructuring upstream, will be back with next release hopefully)

Seems the regular sprints of the Debian Med team have enhanced the team (regarding the number of people and the effectivity of the cooperation). Thanks to all people who joined our effort to make Debian the best free operating system for medical care and biological research.

Bits from Debian Med team (Posted by Andreas Tille)

Hi,

in this bits:

1. Debian Med Bug Squashing Advent Calendar 2011
2. Anniversary of Debian Med
3. Second Debian Med sprint (Southport, 27th-29th January 2012)
4. Mentoring of Month (MoM)
5. DDs who came to Debian because of Debian Med
6. Future plans
7. General lessons learned
   

Debian Med Bug Squashing Advent Calendar 2011

In December last year Thorsten Alteholz has started a nice QA initiative which might be interesting for other teams next Advent. The Debian Med team was able to fix about 70 bugs in this time. Thanks to Thorsten for this nice piece of motivation and thanks to everybody who took part in the bug squashing.

Anniversary of Debian Med

On Mon, 7 Jan 2002 the Debian Med project was first officially announced. I submitted a short blog posting about this and perhaps you might like to see a long sequence of talks about this topic.

Second Debian Med sprint (Southport, 27th-29th January 2012)

In end of January 2012 the Debian Med team has met to the second sprint. As last year I would call this a very successfull event and I would recommend other teams to instanciate such meetings as well. Feel free to read my more verbose report.

Mentoring of Month (MoM)

I have started this project for the following reasons:

• gather more manpower to the team
• strengthen connections to upstream (which might become MoM students)
• help shy people to become more verbose
• to learn myself about potential problems of people who do not feel fit for packaging tasks

I made a short summary how the first MoM project worked (see at bottom).

DDs who came to Debian because of Debian Med

After realising that several members of the Debian Med team finally became DDs I made a little survey to find out about their reasons to become DD / DM. I came to the conclusion that a Blend could be a nice entry point for people to join Debian because newcomers can identify themselves with a known topic (the scope of the Blend - in this case medicine and bioinformatics) first and learn Debian rules in a team with common interest. This perfectly fits my expectation which I had from the beginning 10 years ago and I would be very happy if other Blends would follow this example to be nice, inviting and try to *actively* ask people for cooperation (see some simple rules which I learned in this process below). In the teammetrics GSOC project some graphs were created where you can see the level of contribution of these people (and other team members).

Future plans

Currently some heavy work regarding bringing bibliographic references about packages straight into package information is going on. This topic is specifically interesting in Biology because programs are frequently connected to some publication about the methods used inside the code. This topic is as well relevant to Debian Science and DebiChem. Thanks to the patient work done by Charles Plessy we now have about 70 packages featuring debian/upstream files featuring bibliographic references and there is ongoing work to move these data to UDD to enable further usage. We are in the process of final polishing the format and finishing scripts for the import. If people are interested to join this effort this would be the right moment to raise their hand.

General lessons learned

1. Do not let wait anybody who wants to do work.
2. Newcomers are frequently shy - try to invite them kindly and patiently.
3. Tell people verbosely about your project - it is astonishing how less people know and what wrong assumptions they make about your project.

Kind regards
Andreas.

Report from Debian Med sprint (Posted by Andreas Tille)

The Debian Med team has organised its second sprint in Southport last weekend. This is a report from my personal perspective. I added a short
version of my agenda to the Wiki page.

1. Ensembl packaging specifically working on installation in unstable without any conflicts (=trying to solve libwww issue)
   One main item for this meeting on my agenda was fixing the Ensembl package to finally enable a migration from experimental to unstable. One of the big showstopers is #636923. However, unfortunately the to persons who I urgently needed to discuss this topic did finally not attend and I was only able to determine, that the problem can be stripped down to the problematic package is actually liblwp-parallel-perl. I'll try to keep on working on this.
   


2. The Beast-mcmc finishing
   This package is on my agenda since about one year and I was able to iron out nearly all included binary JAR files. However I get struck on the last problematic JAR mtj.jar is a mess of other included JARs based on f2j blas/arbapck JARs. I reached a state where I got a hint from upstream to the sources for the last JAR in this chain and I need to see whether I will be able to compile. I'll give this a try in the next couple of weeks if not I will push the package to non-free first and leave the final freeing to some later point in
   time. As usual, any help is welcome.
   


3. Continuing with current MoM; presenting MoM to the audience to gather more potential students
   I kept on mentoring the student and there is further progress with the package we are focussing on. Moreover it might be that some participants from the workshop might step in for later Monthes.
   


4. Finishing sofa-framework which needs to be updatet to new version
   Nothing done on this front
   


5. Bug squashing of Debian Med team maintained packages
   Two bugs fixed by new upstream version of GinkgoCADx (#657827, #648167)
   
   
6. If time permits work on some Beast related phylogeny packages
   Uploaded phy-spread package
   


7. Checking status of Debian Med tasks
   The attempt to check the tasks was completely spoiled when noticing that the tools are broken because of technical changes in Debian infrastructure. Sorting this out and enabling regularly updated tasks pages is now on highest position in my priority list.
   


8. Spontaneous mentoring of people
   I gave a spontaneous introductional talk about Debian and Blends structure Moreover I was mentoring Quyen, Laszlo (see list of attendees) and others about gpg keys
   
   
9. Working on Blends sentinel bugs overview
   This was terribly blocked by non-functional fetching translations from ddtp.debian.net which is down. Caring for alternatives to at least get tasks pages updated again but no success so far. (see also item 7) above)
   


10. Helping others packaging and sponsoring
    
    • Sponsored chado (gmod suite) prepared by Olivier Sallou
    • Helped Charles Plessy getting snappy-java using Debian packaged library
    • Worked with Ivo Maintz on copasi
    • Helped Martin Steghöfer with Python packaging
    • Dived a bit into a Ruby package together with Quyen Nguyen with no certain outcome - needs further negotiation with Quyen and other upstream how to proceed
    • Checking the work of Piero Fariselli on three Python packages
    • Had a look with Toni into OpenMicroscopy noticing that it is a beast containing >100 binary JAR files inside the source and will take a talented and very patient Java expert to cope with all this stuff The good news is that upstream was quite supportive to provide a downloadable versioned archive which simplifies obtaining the source Needs (a lot) of further work which I'm unable to do myself
      
    
    
11. License checking
    I was suggesting an ePetition to free Phylip and wrote a first draft for it.
    


12. Mapping Southport :-)
    Added some Hotels and Restaurants to OpenStreetMap
    

Thanks to al participants who joined the workshop and made it a success (again). Looking foreward to next Debian Med workshop.

Also thanks to EagleGenomics for sponsering my travel expenses.

10. anniversary of Debian Med (Posted by Andreas Tille)

I'm happy to announce that the Debian Med project celebrates its 10. anniversary which was announced first at Mon, 7 Jan 2002. I propose to do a small celebration at the Debian Med sprint at end of January in Southport.
I would like to say thanks to everybody who helped the project developing from a single person with a crazy idea who started by picking
up some orphaned biomedical packages to a strong team maintaining a set of over 200 highly specialised packages with a high quality standard. Many thanks - ten years ago I did not imagine that we could reach that a strong state!

New set of metapackages released (Posted by Andreas Tille)

The metapackages which are used to simplify medical applications on Debian GNU/Linux systems were updated in unstable. The most important changes are:

• New metapackage med-oncology recommending package dicompyler
• New metapackage med-rehabilitation recommending package sitplus
• Metapackage med-imaging now recommends package ginkgocadx
• Metapackage med-bio recommends several new packages (as usual)
  

Feel free to install these metapackages and enjoy the new applications on your Debian system.

Debian Med BOF @ DebConf 11 in Banja Luka (Posted by Andreas Tille)

Andreas Tille had a BOF about Debian Med at DebConf 11 in Banja Luka at 30.7.2011. The slides as well as a video record can be downloaded.
Andreas had given an overview about the current status of Debian Med. It can be stated that the project which is one out of several Debian Pure Blends had made good progress over its nine years of existence. While several applications which might be used in medical care in the wider sense (which also stretches to microbiological research) were added to Debian so that we have a count of close to 200 packages it was also stated that the existence of Debian Med itself has attracted new Developers to the Debian project. Saying this Free Software for medicine profits from the Debian distribution and Debian was able to gather new manpower because this software was included.
The following TODO items were raised in the BOF
Visibility:

• Logo
  
• more effective use of social media to attract more users
  
• Work together with Debian Publicity
  
• Release in stable PPA and announce this

Plans for the next Debian Release:

• Hospital information system VistA or at least GT.M (precondition for VistA)
  
• Additional practice management systems FreeMed & FreeMedForms
  
• Further Java packages like Jalview, Beast, Artemis (biology), mayam (medical imaging), dcm4chee (PACS server)
  
• radiation therapy planning Prism
  

2011 Codefest, BOSC and ISMB

Vienna just hosted the Codefest of the Open Bioinformatics Foundation, followed by the Bioinformatics Open Source Conference (BOSC) and the main conference Intelligent Systems in Molecular Biology (ISMB). Debian Med had a talk+poster at BOSC and somehow nobody took that down for the main conference which (for some this may be the proof for the existence of some higher might) let it hang next to the only poster by Microsoft among some 1000 or so. Hillarious. It should be noted that the Microsoft representative, Dr. Simon Mercer, seems to be a nice guy and he did not take it down either.

As a community it was nice to meet many contributors to Debian again, bringing up sweet memories also from January's sprint and Tim to volunteer organising the next one. The Codefest brought preliminary packages for GMOD's chado and jbrowse in collaboration with Scott Cain, who later at BOSC finally met with Olivier, our maintainer of gbrowse. One was also reminded of a series of nice efforts to bring microscopy and its analysis of cellular images closer to Java. And besides ImageJ this also means the need for Fiji. To bring our medical and biological users closer together, those packages have some extra importance to us. After some exchance with respective upstreams, things are getting increasingly ready for our (re)distribution. Michael from the Ensembl helpdesk had a review of the Ensembl packaging and he liked it a lot, which is good. Well, this is not too surprising, since it is maintained by Eagle Genomics - professionals in Ensembl and Cloud Computing ... and sponsors of BOSC. He also encouraged us to submit patches to remove/reduce dependencies on the long outdated version 1.2.3 of BioPerl, so it could leave the experimental section. Jim Procter sees some light towards a Debian package of Jalview. BOSC then brought a series of additional promising contacts and so did the ISMB itself. There is a strong interest from many sides to get getData into a pristine shape. With Peter Rice we have now agreed to get instructions for his EMBOSS tools, maintained by Charles, into it, starting with the classical protein sequence, motif and interaction databases. One is tempted to bring also a text based human genome in from Ensembl, but we'll see how far we get.

A major dominance throughout the Codefest and BOSC in a series of presentations had the Cloud Bio-Linux initiative. Everybody seems to like it, also in industry. It will be described in more detail in a separate post. It deserves it. When Debian approaches the best possible bioinformatics environment (what is that? and for whom?) in a bottom-up approach, Cloud Bio-Linux is top-down: bring something up that works and use Debian technologies whenever this his helpful. They will ask for money, from the government and from industry, earmarked for their bioinformatics ambitions, and from those positive vibes on the conference one tends to think the'll get some. When remembering e.g. the Dunk Tank disaster, anything like that seems rather unlikely to happen from the Debian side. But that is fine. Cloud Bio-Linux is contributing to Debian, and their contributors are feeling to be a part of Debian Med, too.

The community is possibly the most important aspect of it all. The expertise on biomedical computing collected in a single room at the Codefest and BOSC is enormous. And while there are many many many many Macs on many laps, about everyone one talks to uses Ubuntu on their
desktop/servers back home. The Debian Med's repository gives them all an opportunity to bring their expertise up into a collaborative environment and form something larger from there. Last and this year this is the cloud and what you could do with it. Next year brings complete tangible workflows, we are sure.

Gingko-CADx - or - Debian Med is not only about bioinformatics

There is a new package in town, namely Gingko-CADx. This is all about viewing and (for those who want to) also about programming with image data from medical devices. And there are only a handful of packages that render it so obvious why Open Source is about freedom. A couple of years ago I was not so very concerned when I could not immediately read the image data from a befriended clinical institute. My personal eye opener was when I learned that the local Gynecologist could not read the 3D image data but relies on his ultra sound experience and the summary of the Radiologist. I am not so worried about him deciding not to look at it, it is more that this doctor cannot freely make this decision. He does not have the software. Well, he does, now, or to be more exact .. I should go and bring it.

Also in my field, the investigation of complex diseases, image data and their automated analysis is gaining ground. There are movies on the activity of animals, videos counting migrating cells, substances traced in the body ... the more molecular the better. This way, one aims at characterising intermediate phenotypes that are more strongly coupled to genotypic variations, and thus one hopes to better explain the complete disease phenotypes with those additional insights. This is not an academic exercise, but the very start of an understanding that different patients need different treatments. And we will understand better, in what ways the animal models of diseases differ from what one can observe in humans.

So, Open Source once again brings us better communication between doctors, patients and doctors, and between either and statistical geneticists. Yippee.

Community efforts towards research on EHEC

Northern Germany these days experiences many hundreds of infections with severest clinical symptoms by a new strain of E. coli bacteria EHEC subtype. The genome has recently been sequenced only to find out that it is something novel, featuring the EHEC surface markers with something from African strains. No, antibiotics don't work, yes, the number of cases are still increasing, no, the source has not been found.

What would be great to have readily available for everyone are now tools to present some comparative genomics of that strain against the other strains of E. coli sequenced so far. I was very happy to read here http://pathogenomics.bham.ac.uk/blog/2011/06/ehec-genome-assembly/ about collaboratively analysing the raw sequencing data. The next step would then be to look at strain differences and interpret them - on the molecular level and in the clinical context. So, whatever tools we could help promoting to the more clinical researchers, they might be used for a while.

I am not completely sure about what Debian Med could help best with. So, much in line of some earlier blog entry on "doing things with Debian Med" I ask just anyone in contact with researchers working with E. coli (or other pathogenic bacteria) to report on what tools they would like to have available through us or what tools they are already using that Debian Med does not yet provide (so other can have it more easily).

Update [10th of June]: Through the Bioinformatics Computation group at LinkedIn I was pointed to http://enews.patricbrc.org/1172/e-coli-outbreak-new-comprehensive-comparisons/. It looks very nice though I have not any idea yet about how to work with it. And I learned about yet another tool, RAST, standing for 'Rapid Annotation using Subsystem Technology'. More comments, please.

Update [14th of June]: A group in Saarbuecken focuses on regulatory transcriptional motifs of EColi.

Hobbyists

To package for Debian is not difficult. It is just ... different. And once learned, that skill is ubiquitously applicable. Quite some bits that contribute to the motivation to support Debian Med in the first place is to get this kind of software out to the younger ones or just anyone seeking some opportunity to contribute to computational biology, medical informatics or clinical research in some way. This may have some very tangible outcomes, e.g. when you hear that the local doctor cannot read the DVD with images from a PET-CT then this can now be fixed for the next visit. Open Source software definitely can change the world a bit. And the packaging in Debian Med already today helps bringing the software into University Clinics world-wide and to those local doctors that are directly supported by Sebastian and Karsten.

So, if you are out there with an interest in packaging the one or other bit, just say hello on the Debian Med mailing list, please. If English does not come sufficiently easy to you then do not be afraid. At least European languages are well covered and we might find a Debian developer outside the Debian Med community for you to help in your mother tongue.

To not only read the PET-CT data but also deeply impress your doctor, currently there is help needed for a proper packaging of

• Ginkgo-CADx
  

and for the bioinformatics side of Debian Med, a tricky beast to package (one would start with something that works before rendering is perfect) but nonetheless important is

• Jalview
  
• Taverna
  

The task pages (offline for maintenance while I type) of Debian Med show some entries in yellow (need help) and red (missing). Enough to do for everyone.

Who's supporting what ... Debian, Ubuntu, and mutual contributions to Debian Med

A basic idea behind the concept of Blends with Debian is to bring people together that happen to be interested in the same software - users and developers alike ... and to help users developing into developers when interested. Packages are commonly community maintained. When there is some issue spotted with a particular package, it is natural to everyone to fix it when the fix is free of side-effects and easier than writing an email to the regular maintainer. Or when one feels nice. Or when one is the maintainer.

To me, this very much summarises what Debian Med's support is about: once informed about an issue you fix it and/or inform the upstream developers about it. Different people are good at different kind of packages and different kind of problems and then: not everyone is interested in every bug, not everyone is having sufficient time available. So, we all complement each other rather nicely. No guarantees for anything, but trust in the individuals and the community to care. In contrast to the understanding of the term support in a commercial environment, we do not need to improve the packages beyond what upstream has developed. But when we do, then those changes are sent to upstream for an inclusion with the next version to profit everyone, i.e. also Windows or MacOS X users. For our scientific packages such a zero delta to upstream principle is particularly important to remain compatible e.g. with the bioinformatics community at large that may use the same version of a particular tool without our contributions.

Can we also support Ubuntu? Quite a few Debian Developers, Debian Maintainers, package curators and upstream developers are particularly happy to contribute to Debian Med because of Ubuntu's large user base. For them, getting the package into Debian is the way to get packages into Ubuntu. For software that is compatible to the Debian Free Software Guidelines software, the transition from Debian to Ubuntu is just smooth. And concerning support, any problems noticed for any of the packages in Debian Med, which are all on the periphery of the distribution, shall be fixed equally (i.e. no more than once) between the distros. The users and developers of those downstream distributions to Debian then help in spotting things earlier. These thoughts and more led to the initiation of Utnubu (ubuntU spelled backwards) and more recently the Debian Exchange projects. In my personal universe, I always felt Debian Med to be a couple of years ahead of that development. After all, we have subversion and git repositories to maintain our packages. And everyone can contribute to those packaging efforts. And we have a series of developers on Ubuntu who are actively contributing to it.

For users of Debian Med who are not working with the very latest version of their distro, like with oldstable (lenny) or stable (squeeze), 10.04 (lucid) or 10.10 (maverick), our packaging has some difficulties to reach them. They just won't see the recent submissions to the archive. What is not much of an issue for the core functionalities of a distribution, for the scientific edge this may be a problem. There are multiple answers to this:

• as a user: force installation (with --force) and hope for compatibility with the libraries or compile packages yourself, which is easy:
  
  • add deb-src of unstable to the sources.list
    
  • say apt-get source --build packagename
    
  • dpkg -i *.deb
    
• as packagers: organise repositories also for older versions of the distributions
  

For Debian and Ubuntu this are the backports. But only few individuals have upload permissions to those separate repositories. For Ubuntu, and currently discussed also for Debian, there are also Personal Package Archives, in short PPA. Everybody, and any group of everybodies, can have such a repository under their own control. The upload to an older release commonly just means to specify that name in debian/changelog and then create a source-only package by adding the flag "-S" to dpkg-buildpackage. This saves the maintainer to invest all the build time and brings package maintenance down to netbooks and mobile phones so one can do it while waiting for/in the bus :)

Still, to render packages available to older distributions remains manual labour. There is no official support for those elderly distros, be they from Debian or from Ubuntu. To help the situation just a bit, and to grant access to Ubuntu users for those packages that were sent to the experimental section of Debian and/or help overcome the limitation during the freeze of release, a few weeks ago a first Debian Med PPA was created. Let's see what this brings over time.

Some more technical description of the upload from Debian to the PPA: Descriptions on how to upload are linked to the launchpad site. Just, the friendly abbreviations don't work for Debian. So one goes the manual way. The launchpad ftp server (if you are using FTP) does not report the current working directory but "OK"s every cd you make. This is somewhat irritating when using a client that changes to the pub directory upon login. The upload will then fail.
One should rather adopt the typical tools to upload like dput or dupload. The destination (at least for Debian users) needs to be specified manually e.g. for dput as follows:
cat >> ~/.dput.cf <<EOPUT
[debianmedppa]
incoming = ~debian-med/ppa/ubuntu/
fqdn = ppa.launchpad.net
login = anonymous
method = ftp
allow_unsigned_uploads = 0
EOPUT
After locally building the source (or complete) package and signing it, this can then be uploaded with dput debianmedppa packagename*.changes. I cannot say that I have already completely understood every little aspect of launchpad, e.g. I get very much confused about how to distinguish Eucalyptus from their euca2ools. And I am very bad at Bazaar (their version control system). But I like what I have understood and hope they soon start to also support versions of Debian for their PPA and an auto-porting across releases. Debian is now planning for a Debian variant of PPAs. It is really high time for this and should possibly even substitute the experimental section IMHO. If they can afford it and are well advised, then they will also support some downstream distros with it and attempt auto-backports. We'll see.

Gcc 4.6 transition (Posted by Andreas Tille)

Hello,
from gcc 4.4.x with a very short introduction to 4.5.x Debian is now leaping ahead to 4.6.x with several new features. Already coming with 4.5 was the link time optimisation and there are now 128 bit floats. This shall mean something to the molecular dynamics community and maybe others on this list. We also see many more and better optimisations, so everyone will profit this already very present switch to 4.6.x in sid. Phoronix kindly did a benchmark on HMMER with Pfam and MAFFT.
The downside is ... some package builds will break. Thanks to Lucas Nussbaum's tireless QA work the whole Debian archive is rebuilded regularly - so we just know which packages are affected. However, those FTBFS (fails to build from source) cause some work on our side because we need to find out the reason why some package might fail. If we do not fix it the package in question will not reach the next stable release because those issues are regarded "serious" in Debian.
Most of the time, the fixes are rather straight forward. Like, e.g. by

#including <cstddef>

or similar. Please drop comments to this post with whatever strange issue you may have run into. Particularly funny e.g. is the building of Embassy packages for which configure reports a broken gcc. After all, the change to 4.6 is nice to

• send another email to upstream with a patch for them to fix the failure
  
• and while at it, maybe fix something that you wanted to have fixed/modded/... for long, just never got around to it
  
• report to upstream (and this blog maybe) about performance improvements experienced with the new gcc
  
• just enjoy it silently
  

Gcc 4.6 is said not to ship with Ubuntu 11.04, which is unfortunate for Ubuntu but should not hamper the transition of packages. In general those gcc transitions are just enforcing stricter standard compliance of the code and the changes which need to be done in packaging will most probably not break a build with gcc 4.5.
When handling such build failures for your specific package in Debian Med please keep two things in mind:

1. Helping upstream in enhancing their code makes them happy to cooperate with Debian Med and they will probably suggest their users Debian as default distribution if they regard us as competent and helpful partners


2. The role of Debian Med inside Debian will be strengthened if we are quick in fixing our issues. Please keep in mind that the constant growth of Debian always triggers suggestions to drop packages which are not used by many users to keep the maintenance effort lower. By default Debian Med has a small user base (compared to web browsers or office suites etc.) and thus we should really make sure that everybody in Debian knows for sure that the Debian Med packaging team is usually quick in fixing their issues and do not create extra work for other people.

Open Community Research: cross-institutional integrative Bioinformatics - something for Debian Med to aim for in 2012+ ?

A few days ago this blog opened with a series of observations on the multi-directional education and collaboration that comes with an active or passive participation in Debian Med. My personal ambition is to find ways to further institutionalise this constructive exchange beyond packaging. What came to my mind is that this may mean to talk more about actually doing things with our packages.

This will lead us to discussing/optimising/specifying workflows, i.e. the graph connecting data sources with tools and their outputs with other tools plus the optimisation of command line arguments and the evaluation of the findings. This sounds all very natural to me since the desire to complete a particular workflow locally is the motivation to get most packages to the distribution today. Until recently, we just did not have a way to formally talk about those workflows, except for exchanging shell scripts. This has changed with Alan's and Hajo's continued collaboration to get command line tools integrated with the workflow suite Taverna. It allows describing our executables for inputs and outputs and presents them as regular workflow elements, right next to the (today :o) ) dominant remote web services. The myExperiment.org site is a repository of (frequently nested) workflows, with all the typical user comments and ranking. To have that extended for all those bits one can achieve with various tools in Debian will be highly interesting. Admittedly, knowing about the rather limited success in uploading bits as trivial as screenshots, we need much of a positive feedback loop and should not just expect this to be accepted by the community because it could.

So, this leads us to my initial impetus: the community needs something to work on to develop itself and the technologies (like this blog) it has adopted. And this is where public data sets in. We had previously discussed the integration of data with the distribution in the context of BioMaj/getData for curated protein, structure or interaction data. But when we extend that also for some "weird stuff", maybe something novel from the more clinical branch of Debian Med or for the joint (re-?)analysis of a genome (a virus, maybe?) then I have some good confidence that the enormous heterogeneity of us as a community allows us to yield something that a regular institution's Bioinformatics service unit would find difficult to match.

So, we would apply Open Source principles to biomedical (re-)research. Beyond the further development of ourselves, this certainly has many direct benefits through our findings and indirectly because of the education it brings to of all those who are following the development online. Such shared research efforts could start any time, in principle. The anticipated deeper integration of Taverna with our distribution will allow specifying many smallish workflows as legitimate subgoals. Let's hope for some soonish additional posting with a tutorial for Taverna's external tools. With the advent of Ensembl or gbrowse in our distribution we have the sensation of some sort of "completeness" for the end users: once my genome has arrived in either, the work is perceived as done. This may be wrong or right, just filling those web interfaces with data is a challenging workflow. There is quite something to do for it all, still, and we should talk about it.