| 1 |
MAL <mal@×××××××.com> writes: |
| 2 |
|
| 3 |
[ ... ] |
| 4 |
|
| 5 |
> Sorry about replying to my own post, but for the record, downgrading |
| 6 |
> portage to 2.0.46-r12 allowed me to emerge gcc-config successfully |
| 7 |
> and then emerge xpm fine. |
| 8 |
|
| 9 |
gaaah. my apologies, I reported the bug and the same "fix" but |
| 10 |
forgot to include that information. I'll blame the time of night. |
| 11 |
|
| 12 |
<url: http://bugs.gentoo.org/show_bug.cgi?id=16047 > |
| 13 |
|
| 14 |
> Please could someone explain why this happened? Don't want to be |
| 15 |
> stuck on a version of portage forever :/ |
| 16 |
|
| 17 |
I think upgrading to a newer portage will be "safe", but emerging |
| 18 |
gcc-config with the new portage won't be safe. or something like |
| 19 |
that. I'll test things once I eventually get a frigging |
| 20 |
RAID-cabinet working at work and eventually catch some sleep. |
| 21 |
|
| 22 |
-- |
| 23 |
Terje |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives