Bug 116760 - please stablize sys-block/gparted-0.0.9
|
Bug#:
116760
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: blubb@gentoo.org
|
Reported By: blubb@gentoo.org
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: please stablize sys-block/gparted-0.0.9
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2005-12-26 01:15 0000
|
*gparted-0.0.9 (26 Nov 2005)
26 Nov 2005; Simon Stelling <blubb@gentoo.org> +gparted-0.0.9.ebuild:
version bump
It's been in testing for 30 days now, no open bugs, so it is already stable on
amd64.
x86 done
hfsutils and gparted marked stable.
Should we wait until 0.0.9-r1 can be marked stable because of bug #116598
instead? Or do you still want 0.0.9 marked stable?
the only change from 0.0.9 to 0.0.9-r1 is
- xfs? ( sys-fs/xfsprogs )"
+ xfs? ( sys-fs/xfsprogs sys-fs/xfsdump )"
I don't really care which you stablize, but tbh I don't think it's really worth
waiting another 14 days just because of an added dep. So you can either break
the holy policy or stablize 0.0.9 ;) The only reason I asked to stablize -r0
was that I didn't want people shouting at me because I wanted an ebuild stable
that was only a few days old.
Marked ppc stable and we're the last arch, so closing the bug.