Bugs closed in team help

Hi Thorsten, I'm not sure whether you consider Debichem team bugs as valid targets for the advent calendar but I provided some help on a package that shows up on our tasks list[1] and closed #669296 and #872431. Kind regards Andreas. [1] https://blends.debian.org/med/tasks/bio#garlic

Re: December

Hi Aaron, On Fri, Dec 01, 2017 at 10:56:57AM -0500, Aaron M. Ucko wrote: > > Hi, Andreas. Although Cn3D++ comes from the same overarching tree > (NCBI's C++ Toolkit) as BLAST+, it is a separate project. The packaging > work done for BLAST+ would make for a decent starting point, though. Since

Re: SVN to Git migration status

Hi everybody, On Fri, 1 Dec 2017, Andreas Tille wrote: * I never liked the split of one upstream source into lots of SVN checkouts in different source packages. Those who are working on that set of packages need to do stupid repeated work for no good reason and I really

Re: December

Andreas Tille writes: >> I would like to mention #225651 [5] here, as this seems to be the oldest one >> that needs some help (at least a proper closing). > > Pinging Aaron explicitly to refresh his statement given several years ago. Hi, Andreas. Although Cn3D++ comes from

Re: CMake help needed to enable hdf5 for gatb-core (Was: [MoM] Re: gatb-core packaging)

Hi Olivier, On Thu, Nov 30, 2017 at 07:18:59PM +0100, Olivier Sallou wrote: > >> compilation fails later on on json.hpp, but this is an other issue > you removed, for copyright I think, the json.hhp (coming from thirdparty > dir). > It is used to manage json in gatb. The only json.hpp I found in

Re: SVN to Git migration status

Hi Steffen, On Fri, Dec 01, 2017 at 02:06:52PM +0100, Steffen Möller wrote: > > as you know we need to be prepared that when Alioth is moved to some new > > system SVN will not be available any more. So I was busy to migrate > > close to all our packages from SVN to Git. > > That was a

Re: SVN to Git migration status

On 01.12.17 11:23, Andreas Tille wrote: Hi, as you know we need to be prepared that when Alioth is moved to some new system SVN will not be available any more. So I was busy to migrate close to all our packages from SVN to Git. That was a tremendous effort. Many thanks, Andreas. I am

SVN to Git migration status

Hi, as you know we need to be prepared that when Alioth is moved to some new system SVN will not be available any more. So I was busy to migrate close to all our packages from SVN to Git. Close to all means we have the follwing remainings: r-cran-rlumshiny (Git repository created but I'd

Re: build failure on sparc64 of python-biopython

Le ven. 1 déc. 2017 à 11:03, John Paul Adrian Glaubitz < glaub...@physik.fu-berlin.de> a écrit : > Hi Olivier! > > On 12/01/2017 09:24 AM, olivier sallou wrote: > > latest release of python-biopython fails during tests on sparc64 arch > with a *Bus error* (works fine on other archs) > > I have no

Re: build failure on sparc64 of python-biopython

Hi Olivier! On 12/01/2017 09:24 AM, olivier sallou wrote: latest release of python-biopython fails during tests on sparc64 arch with a *Bus error* (works fine on other archs) I have no idea what this could be related to. How could we debug this? This is most likely a result of this particular

Re: December

Hi again, after having fixed the next bug #883047 - hey it was tagged patch and the upload had a diff as simple as diff --git a/debian/changelog b/debian/changelog index d9eab55..2e9a79b 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,10 +1,19 @@ -canu (1.6+dfsg-2) UNRELEASED;

build failure on sparc64 of python-biopython

Hi, latest release of python-biopython fails during tests on sparc64 arch with a *Bus error* (works fine on other archs) I have no idea what this could be related to. How could we debug this? Thanks Olivier