dev-python/ipython dev-python/mistune dev-python/jsonschema dev-python/terminado
Are you sure that dev-python/jsonschema is needed only for USE=notebook or nbconvert? I tried to emerge ipython-3.0.0 with USE="-notebook -nbconvert" and got the error message File "/var/tmp/portage/dev-python/ipython-3.0.0/work/ipython-3.0.0-python2_7/build/lib/IPython/nbformat/validator.py", line 21, in <module> raise ImportError(str(e) + verbose_msg) ImportError: No module named jsonschema IPython notebook format depends on the jsonschema package: https://pypi.python.org/pypi/jsonschema Please install it first. After I installed jsonschema, I got blocked by the bug #541832.
I cannot reproduce this.
So this happens with USE=doc?
+*ipython-2.4.1 (13 Mar 2015) + + 13 Mar 2015; Justin Lecher <jlec@gentoo.org> +ipython-2.4.1.ebuild, + -files/62ipython-gentoo.el, -files/ipython-0.12-globalpath.patch, + -files/ipython-0.13-umlaut.patch, -files/ipython-0.9.1-globalpath.patch, + -files/ipython-1.0.0-setuptools.patch, -ipython-0.10.2.ebuild, + -ipython-1.0.0.ebuild, -ipython-1.2.1.ebuild, -ipython-2.4.0.ebuild, + ipython-2.2.0.ebuild, ipython-3.0.0.ebuild: + Version Bump, bug #539578; fix SLOT operators loosen USE constraints for + USE=doc, bug #542426; don't build API docs for iypthon-3 due to missing + buildtime deps, bug #541832; drop old fixes CVE-2014-3429 bug #517222 and + obsolets bug #486880, bug #489372, bug #489384, bug #428170, bug #407823, bug + #407715, bug #490166, bug #456960, bug #483580, bug #530324, bug #536386 and + bug #481726 +
Looks like ipython reached 3.1 recently
Marked ~ppc64.
(In reply to Leho Kraav (:macmaN @lkraav) from comment #5) > Looks like ipython reached 3.1 recently *ipython-3.1.0 (04 Apr 2015) 04 Apr 2015; Justin Lecher <jlec@gentoo.org> +ipython-3.1.0.ebuild: Version Bump
~/cvsPortage/gentoo-x86/dev-python/ipython $ repoman full RepoMan scours the neighborhood... KEYWORDS.dropped 2 dev-python/ipython/ipython-3.0.0.ebuild: arm mips ppc ppc64 dev-python/ipython/ipython-3.1.0.ebuild: arm mips ppc ppc64 from jsonschema-2.4.0.ebuild KEYWORDS="~amd64 ~x86 ~amd64-linux ~x86-linux" correct me if I'm wrong but jer has made a rare slip and perhaps entered Marked ~ppc64. (Comment 6) into a wrong bug?? This was made <Reported: 2015-02-28> and it appears no progress yet.
retract on Comment 8 that was done 2015-05-20 04:12:57 UTC and I had not cvs up for it, was looking at the state before yesterday, sorry
~arm added
*** Bug 518742 has been marked as a duplicate of this bug. ***
I am confused over pymongo. From ipython-3.2.0.ebuild KEYWORDS="~amd64 ~arm ~ppc64 ~x86 remember still needing ppc added. yet KEYWORDS="~amd64 ~hppa ~x86" from pymongo-2.8.1 and 3.0.3. Why does repoman not report error under the keywords ~arm & ~ppc64 (and add ~ppc) for ipython-3.2.0 annd the freshly bumped ipython-3.2.1?? The bumped ipython-3.2.1 sadly requires version <3. Should these 2 versions of dev-python/pymongo not also be keyworded ~arm & ~ppc64 and ~ppc, which will also pull in dev-db/mongodb/?? Too much to ask?? Or just thank repoman for missing?
Portage currently has ipython-3.2.0.ebuild ipython-3.2.1.ebuild. I suspect the issue over pymongo is explained by a use.mask for IUSE mongodb.
keyworded ~ppc. I'm working on mips but its more demanding.
(In reply to Anthony Basile from comment #14) > keyworded ~ppc. I'm working on mips but its more demanding. I think I'll skip mips. Feel free to close if no one else on the mips team wants to give this one a go.
(In reply to Anthony Basile from comment #15) > (In reply to Anthony Basile from comment #14) > > keyworded ~ppc. I'm working on mips but its more demanding. > > I think I'll skip mips. Feel free to close if no one else on the mips team > wants to give this one a go. KEYWORDS.dropped 2 dev-python/ipython/ipython-3.0.0.ebuild: arm mips ppc ppc64 dev-python/ipython/ipython-3.1.0.ebuild: arm mips ppc ppc64 Both these have since been purged, and I cannot find any revdeps that require mips. I am also curious about 31 Jan 2015; Mike Frysinger <vapier@gentoo.org> ipython-2.3.1.ebuild: Add mips love. and why it was dropped for reasons unknown so soon after. Either way mips appears a memory in the history of ipython. Closing on the basis of the above.
(In reply to Ian Delaney from comment #16) > (In reply to Anthony Basile from comment #15) > > (In reply to Anthony Basile from comment #14) > > > keyworded ~ppc. I'm working on mips but its more demanding. > > > > I think I'll skip mips. Feel free to close if no one else on the mips team > > wants to give this one a go. > > KEYWORDS.dropped 2 > dev-python/ipython/ipython-3.0.0.ebuild: arm mips ppc ppc64 > dev-python/ipython/ipython-3.1.0.ebuild: arm mips ppc ppc64 > > Both these have since been purged, and I cannot find any revdeps that > require mips. I am also curious about > 31 Jan 2015; Mike Frysinger <vapier@gentoo.org> ipython-2.3.1.ebuild: > Add mips love. > > and why it was dropped for reasons unknown so soon after. Either way mips > appears a memory in the history of ipython. Closing on the basis of the > above. 1) If we ever need mips I can do it. I just didn't see the payoff for the time given all the deps. 2) Why is arm ppc and ppc64 in your KEYWORDS.dropped list? Those should be fine?
Anthony that arm mips ppc ppc64 was a copy from Comment 8, 2015-05-21. The state at that time, simply misleading.
