Summary: | sci-biology/bioperl-run ~amd64 keyword request | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ashton Trey Belew <abelew> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED LATER | ||
Severity: | enhancement | CC: | sci-biology |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ashton Trey Belew
2005-10-10 20:16:02 UTC
and I would like to add that 1.5.1 is available now as well: http://news.open-bio.org/archives/2005_10.html#000084 Olivier or sci herd, before we can keyword this ~amd64, please fix the following: *) REQUIRED: bioperl-run requires at least an RDEPEND on bioperl. Most of the perl modules installed by -run have the line "use Bio::Root::Root", which is provided by the base bioperl package Greg: you already filed a bug on that. bug #79459 <-- please amd64: Dependencies are now fixed. Do you want to keyword this? Can you provide test cases outside of the perl-driven make test? make test passed, but mostly for a lack of tools to test with, but when I try running the samples and examples (with a threaded perl, which may or may not be the issue) I get this every time: STACK: Error::throw STACK: Bio::Root::Root::throw /usr/lib64/perl5/vendor_perl/5.8.8/Bio/Root/Root.pm:328 STACK: try{} block /usr/lib64/perl5/vendor_perl/5.8.8/Bio/Tools/Run/Analysis/soap.pm:107 STACK: SOAP::Lite::call /usr/lib64/perl5/vendor_perl/5.8.8/SOAP/Lite.pm:3387 STACK: try{} block /usr/lib64/perl5/vendor_perl/5.8.8/SOAP/Lite.pm:3352 STACK: Bio::Tools::Run::Analysis::soap::input_spec /usr/lib64/perl5/vendor_perl/5.8.8/Bio/Tools/Run/Analysis/soap.pm:305 STACK: ./papplmaker.PLS:137 Also, shouldn't bioperl-run-1.5.1 depend on bioperl-1.5.1 instead of the generic bioperl? (I thought the versions were linked) Quoting from http://www.bioperl.org/wiki/Main_Page : # Core package provides the main parsers, this is the basic package and it's required by all the other packages (bioperl-live CVS directory) # Run package provides wrappers for executing some 60 common bioinformatics applications (bioperl-run in CVS) # Ext package is for C-language extensions including some alignment algorithms and an interface to the Staden IO library (bioperl-ext in CVS). # GUI package includes some basic widgets in Perl-Tk (bioperl-gui in CVS). # BioPerl db is a subproject to store sequence and annotation data in a BioSQL relational database (bioperl-db in CVS). # Pedigree package is for manipulating genotype, marker, and individual data for linkage studies (bioperl-pedigree in CVS) # Microarray package has preliminary objects for manipulating some microarray data formats (bioperl-microarray in CVS) # Network package parses and analyzes protein-protein interaction data (bioperl-network in CVS). # Pipeline package is a project for creating analysis pipelines out of bioperl-run modules (bioperl-pipeline in CVS). File collision during emerge: * checking 366 files for package collisions existing file /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/Bio/.packlist is not owned by this package Searching all installed packages for file collisions... Press Ctrl-C to Stop * sci-biology/bioperl-1.5.1-r1: '/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/Bio/.packlist' Without collision-protect this emerges fine, passes the tests (though most of them are skipped due to missing tools). sci-biology: Can you please provide some test cases so we can make sure this actually works before keywording it? Or are the few tests during emerge enough? The burden is still on sci-biology here, no matter who you reassign it to. We're just looking for some verification of the install working beyond it emerging and passing the tests (that don't seem to be too viable anyway). (In reply to comment #7) > The burden is still on sci-biology here, no matter who you reassign it to. > We're just looking for some verification of the install working beyond it > emerging and passing the tests (that don't seem to be too viable anyway). So how's it going? ;) Sorry, but I have no time for that right now and I am pretty much the only more or less active dev in sci-biology. If amd64 wants to go ahead, that is fine by me, but I cannot provide help at this time. Marking as LATER, feel free to reopen. I'm working on it too Olivier...it just takes me a long time to test things thoroughly... I also watch sci-biology and will help out; however, since I am the only dev in sci-mathematics right now time is pretty scarce at the moment ;) Markus |