Bug 166118 – sys-apps/portage-2.1.2-r9 stable request

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Zac Medico 2007-02-09 19:13:46 UTC]

Arch teams, please test sys-apps/portage-2.1.2-r9 and mark it stable.  There is a new epydoc? ( >=dev-python/epydoc-2.0 ) dependency so that package will also need stable keywords for some archs.

Note that bugs #162453 and #147007 track fixes since 2.1.1.  There is an ewarn message for a behavior change that many users will want to know about:

* In portage-2.1.2, installation actions do not necessarily pull in build time
* dependencies that are not strictly required.  This behavior is adjustable
* via the new --with-bdeps option that is documented in the emerge(1) man page.
* For more information regarding this change, please refer to bug #148870.

[Comment 1 Chris Gianelloni (RETIRED) 2007-02-09 20:31:37 UTC]

Has anyone verified that this will properly build stages?

If not, I can do so.

[Comment 2 Zac Medico 2007-02-09 21:02:19 UTC]

About a month ago, I used catalyst-2.0.1 build x86 stages 1 through 3 with portage-2.1.2_rc4-r5 and everything seemed to work well.  Very little has changed since then, so it should still work just as well with portage-2.1.2-r9.

[Comment 3 Alexander Færøy 2007-02-10 00:07:02 UTC]

Stable on MIPS.

[Comment 4 nixnut (RETIRED) 2007-02-10 07:59:04 UTC]

$ epydocgui
Traceback (most recent call last):
  File "/usr/bin/epydocgui", line 6, in ?
    from epydoc.gui import gui
  File "/usr/lib/python2.4/site-packages/epydoc/gui.py", line 31, in ?
    from Tkinter import *
ImportError: No module named Tkinter

Should epydoc check if python is build with USE="tk"?

[Comment 5 Zac Medico 2007-02-10 08:27:09 UTC]

@python herd: This bug affects all versions of epydoc that install epydocgui (including epydoc-2.1-r2).

(In reply to comment #4)
> $ epydocgui
> Traceback (most recent call last):
>   File "/usr/bin/epydocgui", line 6, in ?
>     from epydoc.gui import gui
>   File "/usr/lib/python2.4/site-packages/epydoc/gui.py", line 31, in ?
>     from Tkinter import *
> ImportError: No module named Tkinter
> 
> Should epydoc check if python is build with USE="tk"?
> 

Yes, and the installation of epydocgui should probably be conditional on USE="tk".

Anyway, that bug has no affect on the portage ebuild since it does not use epydocgui.  It only uses epydoc to generate html documentation at build time.

[Comment 6 Simon Stelling (RETIRED) 2007-02-10 17:04:00 UTC]

amd64 stable

[Comment 7 Raúl Porcel (RETIRED) 2007-02-10 17:23:32 UTC]

x86 stable

[Comment 8 Raúl Porcel (RETIRED) 2007-02-10 17:30:41 UTC]

Readding x86, wrong bug.

Sorry for the bugspam.

[Comment 9 Raúl Porcel (RETIRED) 2007-02-10 17:46:06 UTC]

Okay, now x86 is stable, for real :)

[Comment 10 Jeroen Roovers (RETIRED) 2007-02-10 21:48:54 UTC]

HPPA too.

[Comment 11 Joe Jezak (RETIRED) 2007-02-11 07:41:00 UTC]

As per the suggestion to ignore the epydocgui issue, both epydoc and portage are marked ppc stable.

[Comment 12 Alexander Færøy 2007-02-11 12:32:18 UTC]

Stable on IA64.

[Comment 13 Markus Rothe (RETIRED) 2007-02-11 12:54:13 UTC]

ppc64 stable

[Comment 14 Alexander Færøy 2007-02-11 13:15:35 UTC]

Stable on Alpha.

[Comment 15 Gustavo Zacarias (RETIRED) 2007-02-12 18:04:37 UTC]

sparc stable.

[Comment 16 Chris Gianelloni (RETIRED) 2007-02-13 19:09:06 UTC]

Removing bug #156814 since we don't build releases for ppc-macos (yet)...

[Comment 17 Fabian Groffen 2007-02-13 19:22:55 UTC]

FYI: I hope to soon do something on this bug for ppc-macos

[Comment 18 Fabian Groffen 2007-02-26 18:43:05 UTC]

portage 2.1.2 is completely broken on ppc-macos.  Keyword dropped.  Considering bug as FIXED.