Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 177426 - Rekeyword python ebuilds
Summary: Rekeyword python ebuilds
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Python Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on: 177270
Blocks:
  Show dependency tree
 
Reported: 2007-05-07 09:37 UTC by Bryan Østergaard (RETIRED)
Modified: 2007-06-30 10:29 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
emerge --info (emerge.info-elmer,4.39 KB, text/plain)
2007-05-08 00:44 UTC, Jeroen Roovers (RETIRED) 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bryan Østergaard (RETIRED) gentoo-dev 2007-05-07 09:37:07 UTC 
I've restructered patches, split out python-updater and fixed a good 20 bugs in the new python ebuilds. Due to the split out python-updater and fixing several linker related bugs + changing the way our patches are applied I would like you to test and rekeyword:

python-2.3.6-r1, python-2.4.4-r1 and python-2.5.1.

I plan on unmasking python-2.5 after (most) archs have rekeyworded 2.5.1 assuming I haven't screwed things up completely.
Comment 1 Bryan Østergaard (RETIRED) gentoo-dev 2007-05-07 09:49:28 UTC 
Btw, don't just rely on pythons own tests when keywording. Tests should work but make sure that up- and downgrades also work and be sure to test at least a few python packages as well.
Comment 2 Jeroen Roovers (RETIRED) gentoo-dev 2007-05-08 00:44:47 UTC 
Created attachment 118513 [details]
emerge --info

   Failed tests for dev-lang/python-2.3.6-r1:
test_bsddb
(Not tested in verbose mode)

(1 failed / 211 succeeded)

   Failed tests for dev-lang/python-2.4.4-r2:
229 tests OK.
1 test failed:
    test_bsddb
FAIL: test_previous_last_looping (test.test_bsddb.TestBTree)
FAIL: test_previous_last_looping (test.test_bsddb.TestHashTable)
FAIL: test_previous_last_looping (test.test_bsddb.TestBTree_InMemory)
FAIL: test_previous_last_looping (test.test_bsddb.TestHashTable_InMemory)

   Failed tests for dev-lang/python-2.5.1:
FAIL: test_previous_last_looping (test.test_bsddb.TestBTree)
FAIL: test_previous_last_looping (test.test_bsddb.TestHashTable)
FAIL: test_previous_last_looping (test.test_bsddb.TestBTree_InMemory)
FAIL: test_previous_last_looping (test.test_bsddb.TestHashTable_InMemory)
FAIL: test_previous_last_looping (test.test_bsddb.TestBTree_InMemory_Truncate)

[ebuild  NS   ] dev-lang/python-2.3.6-r1  USE="berkdb doc examples gdbm ipv6 ncurses readline ssl tk -bootstrap -build -nocxx (-nptl) -ucs2" 0 kB [1]
[ebuild     U ] dev-lang/python-2.4.4-r2 [2.4.3-r4] USE="berkdb doc examples%* gdbm ipv6 ncurses readline ssl tk -bootstrap -build -nocxx (-nptl) -ucs2" 0 kB [1]
[ebuild  NS   ] dev-lang/python-2.5.1  USE="berkdb doc examples gdbm ipv6 ncurses readline sqlite ssl tk -bootstrap -build -nocxx (-nptl) -ucs2" 0 kB [1]
Comment 3 Raúl Porcel (RETIRED) gentoo-dev 2007-05-08 16:21:38 UTC 
~ia64 done
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2007-05-10 21:45:02 UTC 
Since I didn't see any response to the bsddb test failures, I assume they are not a problem. Please re-CC hppa@ as needed.
Comment 5 Fabian Groffen gentoo-dev 2007-05-11 08:28:12 UTC 
not keyworded ppc-macos at all, removing from cc.
Comment 6 Bryan Østergaard (RETIRED) gentoo-dev 2007-05-11 22:09:09 UTC 
Alpha and mips done.
Comment 7 Markus Rothe (RETIRED) gentoo-dev 2007-05-12 11:45:33 UTC 
added ~ppc64
Comment 8 Gustavo Zacarias (RETIRED) gentoo-dev 2007-05-14 21:04:21 UTC 
~sparc'd back (and stable 2.4.4-r4 wrt security).
Comment 9 Peter Weller (RETIRED) gentoo-dev 2007-05-19 21:44:13 UTC 
amd64 all done
Comment 10 Lars Weiler (RETIRED) gentoo-dev 2007-06-30 10:29:59 UTC 
ppc done.

Closing this bug, as we are the last arch.