Hi Fabian,
On Tue, Apr 19, 2016 at 02:59:15PM +0200, Fabian Klötzl wrote:
> >>> Cool. Just ping me for sponsering.
> >>
> >> I guess it makes sense, to move the packaging to git, first.
> >
> > Huh? Its at
> >
> > git://anonscm.debian.org/debian-med/mugsy.git
>
> Yeah, but you ported
On 19.04.2016 14:53, Andreas Tille wrote:
> On Tue, Apr 19, 2016 at 02:40:34PM +0200, Fabian Klötzl wrote:
I have some extra patches for those tools, making them up to ten times
faster. Will commit in due course.
>>>
>>> Cool. Just ping me for sponsering.
>>
>> I guess it makes sense,
On Tue, Apr 19, 2016 at 02:40:34PM +0200, Fabian Klötzl wrote:
>
> Yeah, I was lucky that “improving mugsy” was supposed to be my next big
> project at work. Little did we know I had to get past “compiling” first.
:-)
> >> I have some extra patches for those tools, making them up to ten times
Hi,
On 19.04.2016 14:03, Andreas Tille wrote:
> On Tue, Apr 19, 2016 at 12:29:59PM +0200, Fabian Klötzl wrote:
>> Hi Andreas,
>>
>> I spent the last few weeks meandering in the murky marshes of the mugsy
>> source code; It is a monstrosity.
>>
>> [ … lots of whining … ]
>
> Thanks a lot for the
Hi Andreas,
I spent the last few weeks meandering in the murky marshes of the mugsy
source code; It is a monstrosity.
Before answering to your individual points I'd like to stress that I
*literally* spend days trying to compile mugsy with seqan 1.3 which
comes with Ubuntu 14.04 LTS. A hundred
Hi,
I think I need to come back to this nearly one year old mail which I
seem to have left uncommented. It concerns mugsy[1]:
On Sat, 25 Apr 2015 08:52:52 +0200 Andreas Tille wrote:
> On Sat, Apr 25, 2015 at 05:30:39AM +0300, johnhom...@gmail.com wrote:
> > Here's my take on mugsy issues. I
Hi Andrei,
On Sat, Apr 25, 2015 at 05:30:39AM +0300, johnhom...@gmail.com wrote:
Here's my take on mugsy issues. I worked on a tree checked out with:
$ svn checkout svn://svn.code.sf.net/p/mugsy/code/trunk mugsy-code
Building with gcc-4.9.2. The version of boost I compiled it against
Hi Andreas,
Here's my take on mugsy issues. I worked on a tree checked out with:
$ svn checkout svn://svn.code.sf.net/p/mugsy/code/trunk mugsy-code
Building with gcc-4.9.2. The version of boost I compiled it against is 1.56.
I couldn't get it to link, because the authors apparently never
Hello,
I intend to package mugsy which contains a copy (fork?) of some old
seqan version. In contrast to Gert's advise below I would prefer to
port this to the current (and future) seqan versions but I obviously
need some help. The full discussion between Gert and me starts here[2]
in the
Hi,
I've got some request to package mugsy which I started in Git[1]. The
source contained several code copies. I think I sorted out the code
copy of mummer by adding the patches contained in mugsy to the Debian
packaged mummer (see my last upload).
I also tried to get rid of the outdated
Hello Andreas,
I did a
debcheckout --user me git://git.debian.org/debian-med/mugsy.git \
--git-track '*'
and then tried
git-buildpackage -uc -us
which gives me a
gbp:error: upstream/1r2.3+dfsg is not a valid treeish
I guess you have to do a git push --tags.
I also have two
Hi Gert,
On Wed, Apr 15, 2015 at 12:21:07PM +0200, Gert Wollny wrote:
I admit I somehow regret that I had the following GSoC idea to late:
Provide test suites for all Debian Med packages
I think this makes a great GSoC project - we should remember this for
next year.
+1
:-)
Hi Gert,
On Wed, Apr 15, 2015 at 10:53:27AM +0200, Gert Wollny wrote:
gbp:error: upstream/1r2.3+dfsg is not a valid treeish
I guess you have to do a git push --tags.
Done. Sorry for the nuisance.
I also have two dead links in the source tree
mugsyWGA -
Hello Andreas,
I admit I somehow regret that I had the following GSoC idea to late:
Provide test suites for all Debian Med packages
I think this makes a great GSoC project - we should remember this for
next year.
+1
One option to provide some tests in this case could be based on
14 matches
Mail list logo
