Re: Package Fastaq git mess

[Jorge Sebastião Soares <j.s.soares@gmail.com>]

Hey Andreas,

I have everything sorted now. My VM blew up. It was quite a bang.

I was building boost libraries for the next package I'll submit.

Anyway, now that everything is back to normal...

I'm getting this when I try to upload the pristine tar:

js21@builder2:~/deb_alioth/current/fastaq_packaging/fastaq$ git import-orig --pristine-tar ../fastaq_1.5.0.orig.tar.gz
gbp:error:
Repository does not have branch 'upstream' for upstream sources. If there is none see
file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.html#GBP.IMPORT.CONVERT
on howto create it otherwise use --upstream-branch to specify it.

I can checkout the upstream branch with git checkout.

But shouldn't this work straight form the master branch?

My idea at the moment would be to delete the upstream branch form the git repo, recreate it and then upload it.

Does this make any sense?

Regards,

Jorge

On Thu, Oct 9, 2014 at 10:27 AM, Jorge Sebastião Soares <j.s.soares@gmail.com> wrote:

Hey Andreas,

On Thu, Oct 9, 2014 at 10:23 AM, Andreas Tille <andreas@an3as.eu> wrote:

Hi Jorge,

On Thu, Oct 09, 2014 at 09:45:03AM +0100, Jorge Sebastião Soares wrote:
> I think I'm going to delete the fastaq.git project on git alioth and create
> a new project. Since the code is python3 only I will call it python3-fastaq.

Regarding the name:  If it is an *application* please stick to the fastaq
name.  Only python modules should have the python[3]- prefix.

https://github.com/sanger-pathogens/Fastaq

Is a set of scripts that need to be installed for

https://github.com/sanger-pathogens/iva

to run.

In that sense, it sort of is a library. But really as I said above, it's just a set of scripts.

Should I keep the old nomenclature?

Regards,

Jorge