Re: Biomaj package new delivery for bug fixes

Hi Olivier, On Wed, Apr 27, 2011 at 04:53:57PM +0200, Olivier Sallou wrote: > Would you mind uploading it (I do not have yet the maintainer status) I just uploaded the new biomaj package version to make sure the package upgrade issue will be fixed soonish and will not affect more users. However,

Apliec rokas uz vidukļa puskailai sekserītei

Saliec rokas ap pleciem puskailai jaunkundzei, nopērc labu dzērienu pie bāra un noskaties krāšņu šovu.. Jauns un izaicinošs klubs gaida tevi - mēs nešķirojam viesus, mums katrs ir svarīgs: vai no Latvijas, vai Dublinas. Draudzīgas cenas, vāciešu menedžeri - detalizēti uzzini šeitan: http://w

Re: blast+ packaging

Tim Booth writes: > 1) This may have been down to our rubbish wireless link but there > appeared to be something stopping automated downloads (ie. Uscan) from > NCBI. I know they do have anti-leeching on some of their sites. Do you > get any problems? This shouldn't be a problem. How does you

Re: AmpliconNoise ITP

On Wed, Apr 27, 2011 at 03:54:23PM +0100, Tim Booth wrote: > I'm cracking on with a package for AmpliconNoise, which I can't see any > activity for though there is a placeholder on tasks/bio. My > understanding is that a Debian Developer should OK the package and file > an ITP Besides the fact th

Upload of CharLS

Dear all, I am looking for a sponsor for CharLS. CharLS is an implementation of the JPEG-LS standard. This is the internal lib used in GDCM and DCMTK (shipped as convienient lib for now). It appears as being lintian clean. Thanks, -- Mathieu -- To UNSUBSCRIBE, email to debian-med-requ...

Re: AmpliconNoise ITP

Hi Tim, On 04/27/2011 04:54 PM, Tim Booth wrote: I'm cracking on with a package for AmpliconNoise, which I can't see any activity for though there is a placeholder on tasks/bio. Great! My understanding is that a Debian Developer should OK the package only for a first upload to the release o

AmpliconNoise ITP

Hi, I'm cracking on with a package for AmpliconNoise, which I can't see any activity for though there is a placeholder on tasks/bio. My understanding is that a Debian Developer should OK the package and file an ITP so that nobody else starts on their own version. Is that right? Also, who edits t

Biomaj package new delivery for bug fixes

Hi, I have updated the Biomaj package to fix 2 bugs and 1 wishlist. It impacts debian files and adds a patch. Would you mind uploading it (I do not have yet the maintainer status) Thanks Olivier -- gpg key id: 4096R/326D8438 (pgp.mit.edu) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC

Re: blast+ packaging

Hi Olivier, This was on my RADAR but I'm currently about to tackle AmplicoNoise (must remember to file an ITP before I start...) so please go ahead. I had a look at it at the sprint and this is what I found: 1) This may have been down to our rubbish wireless link but there appeared to be somethi

Re: blast+ packaging

Hello, On 04/27/2011 02:35 PM, Olivier Sallou wrote: > I see in tasks the ncbi Blast+ software, not packaged. > > Has anyone started something? Or should I go for it packages/ncbi-tools-cxx I once had a closer look at ... but then there was something with the build the let me stop ... don't reca

Re: blast+ packaging

Hi, thanks for the info. Regarding binaries size vs compiled from source, I know that by default, compilation is done with debug enabled, and increase size/lower performance. For uscan I did not have a look yet, for the moment I will try to get compilation done... The legacy_blast.pl is given i

Re: blast+ packaging

Hi Olivier, On Wed, Apr 27, 2011 at 02:35:55PM +0200, Olivier Sallou wrote: > Has anyone started something? Or should I go for it ? If you are brave enough to tackle this there are several people who would be happy about this (and some other programs depend from it. I would strongly advise to CC

blast+ packaging

Hi, I see in tasks the ncbi Blast+ software, not packaged. Has anyone started something? Or should I go for it ? Olivier -- gpg key id: 4096R/326D8438 (pgp.mit.edu) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438 -- To UNSUBSCRIBE, email to debian-med-requ...@lists.deb

Re: what to do if upgrade is not possible?

Hi Olivier, On Wed, Apr 27, 2011 at 10:39:59AM +0200, Olivier Sallou wrote: > Hi, > shame on me, I have an error in debian scripts of my package preventing > an upgrade of the package (install is ok). There is no real shame on you - that's what is happening when developing software. At first you

what to do if upgrade is not possible?

Hi, shame on me, I have an error in debian scripts of my package preventing an upgrade of the package (install is ok). While I fixed it in the new package (for further updates), in the meanwhile it means that if an upgrade is needed, one must first uninstall the package, then install the new one.