[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [MoM] incorporating phyutility into the packages



Hi Stephen,

On Wed, Mar 12, 2014 at 09:19:10PM -0400, Stephen Smith wrote:
> > any news from your side?
> 
> yeah, sorry about the bit of silence there. I got bogged down in some
> work things. Anyway, back on track. 

:-)
 
> > I noticed you have changed debian/compat but you will definitely get
> > a lintian warning about the fact that debian/control remained at
> > 
> >     debhelper (>= 8)
> > 
> > Can you confirm this?
> 
> Aha, I missed that one. Fixed and committed. 

No problem, fix is OK.
 
> > I noticed that you added your name to Uploaders.  As I said please feel
> > free to take over also the changelog - as said above the most easy way
> > is to use `dch` (see manpage).
> 
> By take over do you mean just rerun  dch --create -v 2.7.3 --package
> phyutility? Or dch -i ?

Well, the result is that your ID is the changelog entry owner (instead
of mine) and the time stamp is updated.  There are a lot of options to
dch and I do not know them all.  The most important thing is the result
once you are leaving the editor which is fired up by dch after some
changes (in principle you can totally ignore dch and fire up the editor
directly ... but for instance to get a proper time stamp dch does a nice
job).

I personally take over packages with

    dch -i

and I also make sure that I reset the increases Debian version (which
is another effect of `dch -i` back to the old version.  When you do this
you will see that also a new paragraph in this changelog section is
created which represents the changes of "Andreas Tille".  Feel free to
delete this since the changelog of a new package should only read

   "Initial release"

and nothing else and finally you want to do this initial release.
  
> > >       cme fix dpkg-copyright
> > > 
> > >     is your friend!
> > 
> > What about this?
> 
> I believe we are good here now. Committed.

Basically.  I made some nitpicking change in the copyright of the

   Files: debian/*

section.  I worked on these in 2012 and you in 2014 (even if you worked
on the upstream code since 2007)
 
> > Any question how to issue an ITP bug?
> > 
> > Just let me know if something remains unclear.  I could easily give
> > more verboes hints if they are needed.
> 
> I think the ITP bug is one that is getting me a little stuck. I
> understand it is the Intent to Package bug, but can't seem to find how
> to close it. If you could point me in the right direction, I think I
> could get it. 

Well, you are opening it by

   reportbug --no-query-bts wnpp

(the --no-query-bts option saves you some time if you know for certain
that there is no such bug.)  Than you are guided by some text based menu
framework.  Please do not forget to add the Debian Med team address (as
in the debian/control file set as Maintainer) once you are asked whether
this bug report should be sended to additional e-mail addresses.

Once you sended this bug report you get a bug number.  This is the
number you should fill in where we currently have ????? in the
debian/changelog file.  If you would have called lintian (did you do so
actually??) it would have told you about a missing bug number which is
exactly the ITP number (new-package-should-close-itp-bug).

> > > Ahh, if there are any publications for phyutility available these
> > > should be mentioned in debian/upstream/metadata.
> > 
> > Feel free to just point me to a publication if existing and I provide a
> > working metadata file. 
> > 
> 
> The publication is this:
> Smith, S. A. and C. Dunn. 2008. Phyutility: a phyloinformatics utility
> for trees, alignments, and molecular data. Bioinformatics. 24: 715-716.
> pdf: http://blackrim.org/files/smithdunn2008.pdf

OK, I added a debian/upstream/metadata file.  One effect of injecting this
will be that on the taskspage section for phyutility[1] the sitation will
be added after the next regeneration cycle of the tasks pages (at latest
in 24 hours).  Please have a look at the file

   debian/upstream/metadata

to understand how to specify citations which is IMHO a nice service to
upstream developers and scientists.

> I am also working on the manpage. I think I know what to do there, just
> getting it together. I think everything should be set then. 

Fine.  I think once the ITP bug is filed the package is ready for upload
... and this only after half of the MoM period!

Thanks for your work on this

    Andreas.

[1] http://blends.debian.org/med/tasks/bio#phyutility 

-- 
http://fam-tille.de


Reply to: