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

Re: Status of BioRuby



On Tue, Oct 06, 2009 at 08:05:59PM +0900, Naohisa GOTO wrote:
> Yes. I'm also a debian user, and I'm glad if I can help.

Ahh, that's really great.  One word beforehand and to everybody (perhaps
I'll compose a separate mail as well): Please install the package
popularity-contest and answer the question whether your data can be
sended to Debian with "Yes" if no specific local policy disallows this.
This helps really to know which packages are used and which not.  For
instance according to

   http://qa.debian.org/popcon.php?package=libbio-ruby1.8

there is no single user of this package.  We know that popularity
contest does not reflect the real number of users.  But it would be
helpful - specifically for speciallised applications like Debian Med is
providing - to know at least of some users.  Otherwise there is the
chance that we might drop a package with no users which would be a
shame for those who are actually happy about Debian packages of the
applications they are using.

Now one minor issue addressed to upstream.  When building the package
some lintian issues are left.  These are:

W: libbio-ruby1.8: binary-without-manpage usr/bin/bioruby
N: 
N:    Each binary in /usr/bin, /usr/sbin, /bin, /sbin or /usr/games should
N:    have a manual page
N:    
N:    Note that though the man program has the capability to check for several
N:    program names in the NAMES section, each of these programs should have
N:    its own manual page (a symbolic link to the appropriate manual page is
N:    sufficient) because other manual page viewers such as xman or tkman
N:    don't support this.
N:    
N:    If the name of the man page differs from the binary by case, man may be
N:    able to find it anyway; however, it is still best practice to make the
N:    case of the man page match the case of the binary.
N:    
N:    If the man pages are provided by another package on which this package
N:    depends, lintian may not be able to determine that man pages are
N:    available. In this case, after confirming that all binaries do have man
N:    pages after this package and its dependencies are installed, please add
N:    a lintian override.
N:    
N:    Refer to Debian Policy Manual section 12.1 (Manual pages) for details.
N:    
N:    Severity: normal, Certainty: possible
N: 
W: libbio-ruby1.8: image-file-in-usr-lib usr/lib/ruby/1.8/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby-bg.gif
N: 
N:    This package installs a pixmap or a bitmap within /usr/lib. According to
N:    the Filesystem Hierarchy Standard, architecture-independent files need
N:    to be placed within /usr/share instead.
N:    
N:    Severity: normal, Certainty: certain
N: 
W: libbio-ruby1.8: image-file-in-usr-lib usr/lib/ruby/1.8/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby-gem.png
W: libbio-ruby1.8: image-file-in-usr-lib usr/lib/ruby/1.8/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/bioruby-link.gif
W: libbio-ruby1.8: image-file-in-usr-lib usr/lib/ruby/1.8/bio/shell/rails/vendor/plugins/bioruby/generators/bioruby/templates/spinner.gif


I think it would be great if you would provide a man page bioruby.1.
The image-file-in-usr-lib issue is probably minor, but if I where you I
would probably adapt to FHS and move the files to /usr/share.  I do not
see a point in changing this for the current Debian package but if you
see a chance to change it for the next BioRuby release this would be
nice.

Finally I just uploaded the new package to unstable and it will be
available after 12 hours at all mirrors.  So you are able to test and
report problems (preferably with patches, because you know we are not
really the Ruby experts or our Ruby experts have time issues).  You
might also consider maintaining the package by becoming a member of the
Debian Med team.  In principle it is not that hard to update an existing
package once the packaging stuff is written.  Just let us know if you
might consider this.  We always are happy about upstream developers in
our team and I hope people here agree with me that we are quite helpful
once it comes to technical Debian details.

We would also welcome if you might announce the existance of the new
Debian packages at BioRuby lists to get more testers.  (Also propagating
the populatity-contest hint would be great.)

Kind regards

        Andreas.

-- 
http://fam-tille.de


Reply to: