Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 265614 - Stabilize sys-apps/coreutils-7.1
Summary: Stabilize sys-apps/coreutils-7.1
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords: STABLEREQ
Depends on: 260533
Blocks: 265037
  Show dependency tree
 
Reported: 2009-04-10 06:15 UTC by SpanKY
Modified: 2009-04-20 05:01 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SpanKY gentoo-dev 2009-04-10 06:15:05 UTC
no known regressions (but plenty of fixes!), except for ccp4 collision ... but i think we should continue on since the sci guys are pretty slow
Comment 1 SpanKY gentoo-dev 2009-04-10 06:29:29 UTC
oh, and before anyone asks, all tests should pass (with sandbox-1.6+)
Comment 2 nixnut (RETIRED) gentoo-dev 2009-04-11 16:36:31 UTC
ppc stable
Comment 3 Tobias Klausmann (RETIRED) gentoo-dev 2009-04-12 10:45:31 UTC
Stable on alpha.
Comment 4 Jeroen Roovers (RETIRED) gentoo-dev 2009-04-12 14:14:16 UTC
Stable for HPPA.
Comment 5 Brent Baude (RETIRED) gentoo-dev 2009-04-12 17:58:15 UTC
ppc64 stable
Comment 6 Markus Meier gentoo-dev 2009-04-18 13:14:16 UTC
amd64/x86 stable
Comment 7 Raúl Porcel (RETIRED) gentoo-dev 2009-04-18 17:17:23 UTC
arm/ia64/sh/sparc stable, you do s390 and m68k :P
Comment 8 Manfred Knick 2009-04-19 08:46:42 UTC
(In reply to comment #0)
> no known regressions 

 >>> Emerging (1 of 11) sys-apps/coreutils-7.1
...
     *** %n in writable segment detected ***

but emerges 'successfully' and removes it's .../temp and .../build.log.

Please judge for your own if you want to consider this as an issue worth a 'bug' of it's own.
Comment 9 SpanKY gentoo-dev 2009-04-20 05:00:10 UTC
not a coreutils issue, plus there have already been bugs filed (and closed) about the issue