Summary: | Stabilize dev-python/enthoughtbase-3.0.6, dev-python/setupdocs-1.0.5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Arfrever Frehtes Taifersar Arahesis (RETIRED) <arfrever> |
Component: | Current packages | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | tomka |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Arfrever Frehtes Taifersar Arahesis (RETIRED)
![]() something is not right when I emerge dev-python/enthoughtbase ask me how add also: dev-python/etsdevtools dev-python/testoob dev-python/traitsgui dev-python/traitsbackendqt dev-python/traits after this, emerge tells me to remove the USE="test" by dev-python/enthoughtbase and then, the packages mentioned are no more pulled in. @Agostino: It is very hard to understand what you mean, please try to be more clear. What I have reconstructed: -) You ran into the good old circular dep in jinja. First install jinja with the doc useflag disabled, then try again. @python: -) There are several missing dependencies, this stabilization will pull in the full traits-package. Can you please ack the following list for x86? dev-python/enthoughtbase-3.0.6 dev-python/setupdocs-1.0.5 dev-python/traits-3.5.0 dev-python/etsdevtools-3.1.0 dev-python/traitsgui-3.5.0 dev-python/traitsbackendqt-3.5.0 dev-python/traitsbackendwx-3.5.0 I have not checked amd64 or ppc, but Agostinos comment suggest that amd64 has no stable version of dev-python/testoob. Please try to do this dependency resolution yourself in the future, it is not the arch teams job. @tomka (In reply to comment #1) > something is not right when I emerge dev-python/enthoughtbase ask me how add > also: > > dev-python/etsdevtools > dev-python/testoob > dev-python/traitsgui > dev-python/traitsbackendqt > dev-python/traits > When i try to emerge enthoughtbase, portage tell me one to one to add this packages, this is clear. > after this, emerge tells me to remove the USE="test" by > dev-python/enthoughtbase and then, the packages mentioned are no more pulled > in. > when I add the last package (traits) to p.keywords, emerge tell me to remove useflag 'test' from enthoughtbase. after removing the useflag test, I realize that the packages that I had added to package.keywords are no longer pulled in. Now is clear? (In reply to comment #3) > > after this, emerge tells me to remove the USE="test" by > > dev-python/enthoughtbase and then, the packages mentioned are no more pulled > > in. What do you mean by portage (or emerge) tells you to remove a USE flag ? You tell portage what to do, right? Something is wrong if you obey the orders of your package manager :) In this case it might be that you told portage to emerge the package with USE="-test" ? (Note that FEATURES="test" implies USE="test") In this case the packages above are not pulled in anymore because this dependency is conditional on USE="test". You can read about USE-conditional (and other)dependencies here: http://devmanual.gentoo.org/general-concepts/dependencies/index.html It will also be useful to read man 5 ebuild and look at a few ebuilds to understand what is going on. Also make sure that you have read the manual pages man portage man emerge Sorry for hijacking this bugreport, back to business. (In reply to comment #2) Stabilize the newest version of all required packages. (In reply to comment #5) > (In reply to comment #2) > > Stabilize the newest version of all required packages. > Ok, almost done: =dev-python/enthoughtbase-3.0.6 fails tests because they depend on scipy. Please add. Doctest: enthought.util.tree.tree_zip ... ok ====================================================================== ERROR: Failure: ImportError (No module named scipy) ---------------------------------------------------------------------- Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/nose/loader.py", line 382, in loadTestsFromName (In reply to comment #6) Only deprecated enthought.util.numeric module depends on scipy. The test, which requires this module is now skipped when scipy isn't installed. x86 did the list in comment #2, but this does not mean that it is right for ${yourarch}. For instance If I just read that repoman warning correctly enthoughtbase-3.0.6 does not even have ~ppc. PPC team can fix bug #341627 and bug #347107 at the same time. (In reply to comment #7) > (In reply to comment #6) > > Only deprecated enthought.util.numeric module depends on scipy. The test, which > requires this module is now skipped when scipy isn't installed. > Can you please provide a clear list ? I am really confused with the comments You should only read comments #0 and #5. Probable list for amd64:
>=dev-python/enthoughtbase-3.0.6
>=dev-python/etsdevtools-3.1.0
>=dev-python/setupdocs-1.0.5
>=dev-python/testoob-1.15
>=dev-python/traits-3.5.0
>=dev-python/traitsbackendqt-3.5.0
>=dev-python/traitsbackendwx-3.5.0
>=dev-python/traitsgui-3.5.0
ppc done dev-python/testoob wasn't actually used and no longer needs to be stabilized. amd64 done |