Re: Lets maintain libbpp-phyl-omics in Debian Med team
Hi Julien,
On Mon, Apr 11, 2016 at 09:10:00AM +0200, Julien Yann Dutheil wrote:
> I will look at the bug (and try to compile with gcc6 for a check of all
> libs. As for bpp-seq, I think it is because it needs some input files that
> should be in the test folder too (eg example.fasta, example.aln and
> example.ph).
I have verified that these files are existing in the very same folder as
the test code. I'm not sure whether this is the correct location for
these files since may be the test code will be started from a different
folder (I tried a patch adding "test/" in front of the file names but
this did not helped. I also tried deactivating single tests inside
test_io - also with no success.
> Just a pragmatic question: If I would like to include these in the 2.2.0
> version, how can I do that with tags? I mean, we created a dedicated branch
> for each stable version so that it's easy to include such fixes and not all
> the further modification that might have happened on the master branch.
> With tags, that would be like inserting a commit back in time, just before
> the tagged commit... is that possible? (Sorry for my still poor knowledge
> of git, I just know the few commands that I'm using on a daily basis :s)
I admit I do not work with Github and if there are any specifics. But
tagging something back in time should be no problem at all. As far as
I know the branch also does not matter. You go to the commit that was
released as version 2.2.0 (and reflects the content of the release
tarball) and than you add a tag to this.
[This mail goes in CC to the Debian Med list - others might correct me
if I'm wrong.]
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: