Summary: | proposed 2006.1 profile for ppc64 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markus Rothe (RETIRED) <corsair> |
Component: | [OLD] Core system | Assignee: | ppc64 architecture team <ppc64> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | frederic.grosshans_web |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 139151 |
Description
Markus Rothe (RETIRED)
2006-07-04 07:34:08 UTC
I've found no other way to emerge gcc-4 and glibc-2.4 (package.unmask doesn't change anything), which keeps my toolchain in a bad state with no possibility to repair it (gcc-3.4.6 and glibc-2.4, portage wants to emerge glibc-2.3.6,but can't downgrade glibc). This bug being kept unresolved causes me big trouble. If you don't want to make this change quickly, could you mask the glibc-2.4 and gcc-2.4 packages in the 2006.0 profile using the package.mask file instead of the packages file ? It would allow to unmask them. (In reply to comment #1) > > If you don't want to make this change quickly, could you mask the glibc-2.4 and > gcc-2.4 packages in the 2006.0 profile using the package.mask file instead of > the packages file ? It would allow to unmask them. > Answer to myself: this part is stupid ! I misunderstood the package.mask package. (thanks to mabi on #gentoo-ppc ) (In reply to comment #1) > I've found no other way to emerge gcc-4 and glibc-2.4 (package.unmask doesn't > change anything), which keeps my toolchain in a bad state with no possibility > to repair it (gcc-3.4.6 and glibc-2.4, portage wants to emerge glibc-2.3.6,but > can't downgrade glibc). The workaround to override the profile (tahnks SpanKY !) is to create the file /etc/portage/profile/packages with the following lines -<sys-libs/glibc-2.4 -<sys-devel/gcc-4 dostrow added 2006.1 profiles. newer click on the wrong place.. marking as FIXED closing |